Triple
T29422711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARTEC GmbH |
E746196
|
entity |
| Predicate | vehicleRoleDeveloped |
P15904
|
FINISHED |
| Object | multirole armoured fighting vehicle |
—
|
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: multirole armoured fighting vehicle | Statement: [ARTEC GmbH, vehicleRoleDeveloped, multirole armoured fighting vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRoleDeveloped Context triple: [ARTEC GmbH, vehicleRoleDeveloped, multirole armoured fighting vehicle]
-
A.
vehicleDeveloped
chosen
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
-
B.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
C.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
D.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
E.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6aa3d08190887bfa4eed48faeb |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:06 p.m.