Triple
T37452700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bone Wars |
E930709
|
entity |
| Predicate | mainDiscoveryLocation |
P97373
|
FINISHED |
| Object | Morrison Formation |
—
|
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: Morrison Formation | Statement: [Bone Wars, mainDiscoveryLocation, Morrison Formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDiscoveryLocation Context triple: [Bone Wars, mainDiscoveryLocation, Morrison Formation]
-
A.
mainDiscoverySite
chosen
Indicates the primary location where something (such as an object, specimen, or phenomenon) was originally discovered.
-
B.
discoveryTarget
Indicates that one entity is the object, subject, or focus that another entity discovers or aims to discover.
-
C.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
D.
discoveryScope
Indicates the extent or range within which something can be found, detected, or identified.
-
E.
hasDiscoveryFacility
Indicates that an entity has, is associated with, or is served by a facility where discoveries (such as scientific, medical, or technological findings) are made or were made.
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.