Triple
T28908125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Ulan IFV |
E733141
|
entity |
| Predicate | turretManufacturer |
P165517
|
FINISHED |
| Object | Steyr-Daimler-Puch Spezialfahrzeug |
—
|
NE NERFINISHED |
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: Steyr-Daimler-Puch Spezialfahrzeug | Statement: [Austrian Ulan IFV, turretManufacturer, Steyr-Daimler-Puch Spezialfahrzeug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turretManufacturer Context triple: [Austrian Ulan IFV, turretManufacturer, Steyr-Daimler-Puch Spezialfahrzeug]
-
A.
turret
Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
-
B.
turretBasedOn
Indicates that one turret is derived from, modeled after, or constructed using the design or components of another turret.
-
C.
turretDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a turret associated with another entity.
-
D.
hasTurrets
Indicates that an entity is equipped with or possesses one or more turrets.
-
E.
turretCrew
Indicates that an entity serves as a crew member operating or manning a turret associated with another entity.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65adbd0c481909b11c92ac9aebea4 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 8:09 a.m.