Triple
T37053047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Walker Lindh |
E917099
|
entity |
| Predicate | militaryGroupSupported |
P193028
|
FINISHED |
| Object | Taliban |
—
|
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: Taliban | Statement: [John Walker Lindh, militaryGroupSupported, Taliban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryGroupSupported Context triple: [John Walker Lindh, militaryGroupSupported, Taliban]
-
A.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
B.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
C.
usesMilitaryUnit
Indicates that one entity employs, deploys, or otherwise makes operational use of a specific military unit.
-
D.
militaryBranchTestedBy
Indicates that a particular military branch is the subject of testing, evaluation, or experimentation by a specified agent or process.
-
E.
isCombatSupportUnit
Indicates that the unit’s primary role is to provide operational or logistical support to combat forces rather than engage directly in frontline fighting.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:14 p.m.