Triple
T7575612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cuckooshrikes |
E179355
|
entity |
| Predicate | typicalStratum |
P40392
|
FINISHED |
| Object | forest canopy |
—
|
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: forest canopy | Statement: [cuckooshrikes, typicalStratum, forest canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStratum Context triple: [cuckooshrikes, typicalStratum, forest canopy]
-
A.
strataAre
Indicates that one or more entities are classified as geological or structural layers (strata) in relation to something else.
-
B.
typeStratum
chosen
Indicates that one entity is classified as a geological or conceptual layer or stratum within which the other entity is situated or to which it belongs.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
stratotypeSection
Indicates the reference rock section formally designated as the standard or type example for a particular stratigraphic unit or boundary.
-
E.
stratotypeRegion
Indicates the region or geographic area that serves as the reference or standard location (stratotype) for a particular stratigraphic unit or interval.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94a25148190b5b76e000e0336c4 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.