Triple
T31668270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemon |
E808192
|
entity |
| Predicate | botanicalNameOfTree |
P172613
|
FINISHED |
| Object | Citrus limon |
—
|
NE NERFINISHED |
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: Citrus limon | Statement: [Lemon, botanicalNameOfTree, Citrus limon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: botanicalNameOfTree Context triple: [Lemon, botanicalNameOfTree, Citrus limon]
-
A.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
B.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or context.
-
C.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
-
D.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
E.
prefersTreeGenus
Indicates that one entity has a preference for trees belonging to a particular genus over other tree genera.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 11 p.m.