Triple
T11087195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shivering Timbers |
E262150
|
entity |
| Predicate | firstDropAngle |
P97147
|
FINISHED |
| Object | approximately 55 degrees |
—
|
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: approximately 55 degrees | Statement: [Shivering Timbers, firstDropAngle, approximately 55 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDropAngle Context triple: [Shivering Timbers, firstDropAngle, approximately 55 degrees]
-
A.
firstDisplacement
Indicates the initial change in position of an entity from its starting point in a given context or sequence of movements.
-
B.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
C.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
E.
first
Indicates that one entity precedes all others in an ordered sequence or ranking.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c5008081908f59612243fa4f7a |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.