Triple
T29456003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dashnaktsutyun |
E747101
|
entity |
| Predicate | hasArmedWingHistorically |
P149849
|
FINISHED |
| Object | fedayeen units |
—
|
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: fedayeen units | Statement: [Dashnaktsutyun, hasArmedWingHistorically, fedayeen units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArmedWingHistorically Context triple: [Dashnaktsutyun, hasArmedWingHistorically, fedayeen units]
-
A.
hasArmedWing
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
B.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
C.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
D.
hasMilitaryWingHistory
chosen
Indicates that an entity has, or has had in the past, an associated military wing or armed branch as part of its history.
-
E.
hasPlayedWingFor
Indicates that one entity has played in the wing position (typically in a sports context) for another entity, such as a team or organization.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 3:36 p.m.