Triple
T29298017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joinvilleaceae |
E742883
|
entity |
| Predicate | APGIIIPlacement |
P103577
|
FINISHED |
| Object | Poales |
—
|
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: Poales | Statement: [Joinvilleaceae, APGIIIPlacement, Poales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: APGIIIPlacement Context triple: [Joinvilleaceae, APGIIIPlacement, Poales]
-
A.
APGIVPlacement
Indicates the placement or positioning of an APGIV element relative to another entity or reference point.
-
B.
APGSystemPlacement
Indicates a relationship where an APG (Auxiliary Power Generation) system is positioned, installed, or located relative to another object or environment.
-
C.
APGIIISystem
chosen
Indicates a classification relationship where entities are organized according to the APG III (Angiosperm Phylogeny Group III) taxonomic system.
-
D.
apogeeLocation
Indicates the location in space where an orbiting object is at its farthest point (apogee) from the body it orbits.
-
E.
apexLocation
Indicates the specific point or region that serves as the highest or most pointed part (apex) of an object or structure.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654594048190ad15dbcd2c16db2e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:08 p.m.