Triple
T149876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger 2 |
E3407
|
entity |
| Predicate | turretTraverse |
P6072
|
FINISHED |
| Object | 360 degrees |
—
|
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: 360 degrees | Statement: [Challenger 2, turretTraverse, 360 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretTraverse Context triple: [Challenger 2, turretTraverse, 360 degrees]
-
A.
tunnelCircumference
Indicates the circular distance around the inner boundary of a tunnel’s cross-section.
-
B.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
C.
towerShape
Indicates that one entity has the physical form or outline of a tower in relation to another entity.
-
D.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.