Triple
T28153091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion Condor |
E714672
|
entity |
| Predicate | groundEquipmentUsed |
P101141
|
FINISHED |
| Object | Panzer I |
—
|
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: Panzer I | Statement: [Legion Condor, groundEquipmentUsed, Panzer I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundEquipmentUsed Context triple: [Legion Condor, groundEquipmentUsed, Panzer I]
-
A.
notableGroundEquipment
Indicates that there is ground-based equipment at or associated with an entity that is considered significant or noteworthy in some context.
-
B.
typeOfEquipmentUsed
chosen
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
C.
hasAuxiliaryEquipment
Indicates that one entity is equipped with, or accompanied by, additional supporting equipment associated with another entity.
-
D.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
E.
landingGearType
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641789c90819081eb1c857d032025 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10 p.m.