Triple
T31506154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musée des Blindés |
E803821
|
entity |
| Predicate | vehiclesOperational |
P172570
|
FINISHED |
| Object | about 200 vehicles |
—
|
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 vehicles | Statement: [Musée des Blindés, vehiclesOperational, about 200 vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehiclesOperational Context triple: [Musée des Blindés, vehiclesOperational, about 200 vehicles]
-
A.
throughCarsOperateWith
Indicates that vehicles operate or move through an area, system, or route in coordination or interaction with another specified element.
-
B.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
C.
vehicleFunction
Indicates the functional role or primary purpose that a vehicle is designed or used to perform.
-
D.
controlVehicle
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
E.
servicesRollingStock
Indicates that an entity provides operational services to or performs work on rolling stock (such as trains or rail vehicles).
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 9:47 p.m.