Triple
T31690498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liriodendron tulipifera |
E808774
|
entity |
| Predicate | budDescription |
P172422
|
FINISHED |
| Object | valvate buds |
—
|
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: valvate buds | Statement: [Liriodendron tulipifera, budDescription, valvate buds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budDescription Context triple: [Liriodendron tulipifera, budDescription, valvate buds]
-
A.
badgeDescription
Indicates the textual explanation or details that describe what a particular badge represents or signifies.
-
B.
boonDetails
Indicates the specific terms, conditions, or characteristics associated with a granted benefit or favor within the relationship or action.
-
C.
backDescription
Indicates that an entity provides a description or textual information specifically about the back side or rear view of another entity.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
cargoDescription
Indicates that one entity provides a textual description or details about the cargo associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:08 p.m.