Triple
T35947018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhoiptelea |
E1039610
|
entity |
| Predicate | previousSystemPlacement |
P125828
|
FINISHED |
| Object | Rhoipteleaceae |
—
|
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: Rhoipteleaceae | Statement: [Rhoiptelea, previousSystemPlacement, Rhoipteleaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousSystemPlacement Context triple: [Rhoiptelea, previousSystemPlacement, Rhoipteleaceae]
-
A.
previousPlacement
Indicates that one entity occupied a position, role, or location before another specified placement or assignment.
-
B.
previousSubfamilyPlacement
chosen
Indicates that an entity was formerly assigned to a different subfamily before its current taxonomic placement.
-
C.
previousSystemName
Indicates that an entity was formerly known by a different system name prior to its current designation.
-
D.
previousLocationReplaced
Indicates that one location has been superseded or taken over by another location, replacing its previous role or position.
-
E.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:07 p.m.