Triple
T2597894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyctaginaceae |
E58273
|
entity |
| Predicate | APGIVPlacement |
P40130
|
FINISHED |
| Object | order Caryophyllales |
—
|
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: order Caryophyllales | Statement: [Nyctaginaceae, APGIVPlacement, order Caryophyllales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: APGIVPlacement Context triple: [Nyctaginaceae, APGIVPlacement, order Caryophyllales]
-
A.
APGSystemPlacement
Indicates a relationship where an APG (Auxiliary Power Generation) system is positioned, installed, or located relative to another object or environment.
-
B.
fieldPlacementComponent
Indicates that one entity functions as a component or sub-part within the field placement structure or configuration of another entity.
-
C.
bombPlacement
Indicates the act of positioning or installing a bomb at a specific location or target.
-
D.
enginePlacement
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
E.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4548b1081909d28f88ea5e14202 |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd2baee308190bdaa41ef1f6bc9cc |
completed | March 7, 2026, 7:24 a.m. |
Created at: March 6, 2026, 9:49 p.m.