Triple
T14645227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirage IIIR |
E343827
|
entity |
| Predicate | sensorPlacement |
P79888
|
FINISHED |
| Object | nose section |
—
|
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: nose section | Statement: [Mirage IIIR, sensorPlacement, nose section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensorPlacement Context triple: [Mirage IIIR, sensorPlacement, nose section]
-
A.
slotLocation
chosen
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
-
B.
positioningSystems
Indicates a relationship where systems are used to determine, track, or control the spatial position or location of entities.
-
C.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
-
D.
APGSystemPlacement
Indicates a relationship where an APG (Auxiliary Power Generation) system is positioned, installed, or located relative to another object or environment.
-
E.
bombPlacement
Indicates the act of positioning or installing a bomb at a specific location or target.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ea6d8481908e6331ca173c646b |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.