Triple
T37452619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland-Lloyd Quarry |
E930707
|
entity |
| Predicate | dominantTaxon |
P38050
|
FINISHED |
| Object | Allosaurus fragilis |
—
|
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: Allosaurus fragilis | Statement: [Cleveland-Lloyd Quarry, dominantTaxon, Allosaurus fragilis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantTaxon Context triple: [Cleveland-Lloyd Quarry, dominantTaxon, Allosaurus fragilis]
-
A.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
B.
hasDominantSpecies
chosen
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
C.
dominantTreeCommonName
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
-
D.
dominantLifeformType
Indicates which type of lifeform holds primary dominance or control within a given context or environment.
-
E.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.