Triple
T24611130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuber magnatum Pico |
E609115
|
entity |
| Predicate | glebaAppearance |
P66799
|
FINISHED |
| Object | marbled with white veins |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: marbled with white veins | Statement: [Tuber magnatum Pico, glebaAppearance, marbled with white veins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glebaAppearance Context triple: [Tuber magnatum Pico, glebaAppearance, marbled with white veins]
-
A.
describesAppearanceOf
Indicates that one entity provides information about the visual characteristics or outward look of another entity.
-
B.
glaze
Indicates that an agent coats or covers a surface of an entity with a smooth, often shiny or protective, layer or substance.
-
C.
colorOfGleba
chosen
Indicates the color characteristic of the gleba (the spore-bearing inner tissue) of a fungus.
-
D.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
E.
coreAppearance
Indicates that one entity serves as the primary or defining visual form or look of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.