Triple
T38517189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z1 truss |
E922371
|
entity |
| Predicate | initiallyMounted |
P91248
|
FINISHED |
| Object | P6 truss |
—
|
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: P6 truss | Statement: [Z1 truss, initiallyMounted, P6 truss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyMounted Context triple: [Z1 truss, initiallyMounted, P6 truss]
-
A.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
B.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
C.
mountedAtFocus
Indicates that one entity is physically or logically attached or fixed at a specific focal point or position on another entity.
-
D.
hasInitialState
chosen
Indicates that an entity begins or is configured with a specified starting condition or state.
-
E.
hasMountingStyle
Indicates the method or configuration by which one entity is physically attached, fixed, or mounted to another surface or structure.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:32 p.m.