Triple
T37093071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-111 |
E918477
|
entity |
| Predicate | issTrussOrMobileElementInstalled |
P187134
|
FINISHED |
| Object | Mobile Base System |
—
|
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: Mobile Base System | Statement: [STS-111, issTrussOrMobileElementInstalled, Mobile Base System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issTrussOrMobileElementInstalled Context triple: [STS-111, issTrussOrMobileElementInstalled, Mobile Base System]
-
A.
isMovableBridge
Indicates that a bridge is designed to move (e.g., lift, swing, or open) to allow passage of traffic such as ships or boats.
-
B.
isVehicularBridge
Indicates that the subject is a bridge specifically designed and constructed to carry vehicular traffic.
-
C.
hasTunedMassDamper
Indicates that an entity is equipped with or incorporates a tuned mass damper as part of its structure or system.
-
D.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
E.
hasSteelStructure
Indicates that one entity incorporates or is built with a structural framework made of steel in relation to another entity.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.