Triple
T2958923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panzer II |
E79998
|
entity |
| Predicate | operationalRangeRoad |
P25150
|
FINISHED |
| Object | about 200 km |
—
|
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: about 200 km | Statement: [Panzer II, operationalRangeRoad, about 200 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalRangeRoad Context triple: [Panzer II, operationalRangeRoad, about 200 km]
-
A.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
B.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadOperator
Indicates that one entity is responsible for operating, managing, or maintaining a particular road or road network.
-
D.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
E.
operationalRange
chosen
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.