Triple
T37881354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAR-93 Vultur |
E944872
|
entity |
| Predicate | YugoslavPartnerManufacturer |
P42639
|
FINISHED |
| Object | SOKO |
—
|
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: SOKO | Statement: [IAR-93 Vultur, YugoslavPartnerManufacturer, SOKO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: YugoslavPartnerManufacturer Context triple: [IAR-93 Vultur, YugoslavPartnerManufacturer, SOKO]
-
A.
hasTypeDuringYugoslavia
Indicates that an entity had a particular type or classification specifically during the historical period of Yugoslavia.
-
B.
currentSuccessorStateOnYugoslavSide
Indicates that the subject is recognized or treated as the present successor state on the Yugoslav side in a given political or legal context.
-
C.
isSovietCounterpartOf
Indicates that one entity serves as the Soviet-era equivalent or counterpart to another entity in role, function, or status.
-
D.
stanceOnYugoslavia
Indicates a subject’s position, attitude, or policy toward Yugoslavia as a political or historical entity.
-
E.
formerManufacturerPartner
chosen
Indicates that two entities were previously in a manufacturer–partner business relationship, but that partnership has since ended.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.