Triple
T15387687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nothofagus dombeyi |
E367957
|
entity |
| Predicate | canopyRole |
P118582
|
FINISHED |
| Object | dominant canopy species |
—
|
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: dominant canopy species | Statement: [Nothofagus dombeyi, canopyRole, dominant canopy species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canopyRole Context triple: [Nothofagus dombeyi, canopyRole, dominant canopy species]
-
A.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
B.
LeafRole
Indicates that an entity functions as a terminal or lowest-level role in a hierarchical structure, with no subordinate roles beneath it.
-
C.
coastRole
Indicates a role or function that an entity has specifically in relation to a coast or coastal area.
-
D.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
E.
roleOnAtlasV
Indicates that an entity holds a specific role or function in relation to the Atlas V launch vehicle or program.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.