Triple
T31690497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liriodendron tulipifera |
E808774
|
entity |
| Predicate | twigDescription |
P11875
|
FINISHED |
| Object | slender twigs with diaphragmed pith |
—
|
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: slender twigs with diaphragmed pith | Statement: [Liriodendron tulipifera, twigDescription, slender twigs with diaphragmed pith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twigDescription Context triple: [Liriodendron tulipifera, twigDescription, slender twigs with diaphragmed pith]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describedFrom
Indicates that something is characterized, explained, or defined based on information, perspective, or features originating from a particular source or reference point.
-
C.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
D.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
E.
unitDescription
Indicates that a textual description is provided explaining the characteristics or details of a unit.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:08 p.m.