Triple
T7526218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 22 |
E177898
|
entity |
| Predicate | orientationType |
P77331
|
FINISHED |
| Object | magnetic |
—
|
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: magnetic | Statement: [Runway 22, orientationType, magnetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationType Context triple: [Runway 22, orientationType, magnetic]
-
A.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
orientationPrinciple
Indicates the guiding rule or standard that directs how something is positioned, aligned, or oriented in relation to other things.
-
C.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
D.
orientationProperty
Indicates that one entity has a specific spatial or directional orientation in relation to another entity or reference frame.
-
E.
valueOrientation
Indicates how an entity’s preferences, priorities, or attitudes are directed toward particular values or value systems.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f555455c81908850210bcad96ac2 |
completed | March 27, 2026, 9:23 p.m. |
Created at: March 27, 2026, 3:46 p.m.