Triple
T5267690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalton Highway |
E118976
|
entity |
| Predicate | requiresPreparation |
P100
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dalton Highway, requiresPreparation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPreparation Context triple: [Dalton Highway, requiresPreparation, true]
-
A.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
B.
preparationInvolved
Indicates that a particular preparation, process, or setup is involved in enabling or carrying out an action, event, or relationship.
-
C.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.