Triple
T35358554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conocarpus |
E1021404
|
entity |
| Predicate | Conocarpus lancifolius_commonName |
P183053
|
FINISHED |
| Object | damas tree |
—
|
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: damas tree | Statement: [Conocarpus, Conocarpus lancifolius_commonName, damas tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Conocarpus lancifolius_commonName Context triple: [Conocarpus, Conocarpus lancifolius_commonName, damas tree]
-
A.
Conocarpus erectus_commonName
chosen
Indicates that a common (vernacular) name is assigned to the species Conocarpus erectus.
-
B.
Conocarpus erectus_nativeRange
Indicates that the native geographic range or region where *Conocarpus erectus* naturally occurs is the specified place.
-
C.
botanicalNameOfTree
Indicates that one entity is the scientific (botanical) name corresponding to a given tree entity.
-
D.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
E.
ImperialPalmTrunks
Indicates a relationship where objects are identified specifically as trunks of imperial palm trees.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:03 p.m.