Triple
T7968944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow Development |
E185275
|
entity |
| Predicate | spaceMountainEngineeringRole |
P80058
|
FINISHED |
| Object | design of coaster track and train system |
—
|
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: design of coaster track and train system | Statement: [Arrow Development, spaceMountainEngineeringRole, design of coaster track and train system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceMountainEngineeringRole Context triple: [Arrow Development, spaceMountainEngineeringRole, design of coaster track and train system]
-
A.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
-
B.
cableCarOperator
Indicates that one entity operates, manages, or runs a cable car service for another entity or location.
-
C.
chiefEngineer
Indicates that one entity serves as the primary or lead engineer responsible for overseeing engineering activities for another entity.
-
D.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
E.
spaceSectorRole
Indicates the functional role or responsibility an entity holds within a specific space sector or domain.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:13 p.m.