Triple
T23881890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Services Bureau for Afghan Mujahideen |
E600224
|
entity |
| Predicate | hadKeyMember |
P44793
|
FINISHED |
| Object | Osama bin Laden |
—
|
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: Osama bin Laden | Statement: [Services Bureau for Afghan Mujahideen, hadKeyMember, Osama bin Laden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadKeyMember Context triple: [Services Bureau for Afghan Mujahideen, hadKeyMember, Osama bin Laden]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
keyMember
chosen
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
C.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
-
D.
hadKeyIssue
Indicates that an entity experienced a primary or critical problem related to a key aspect, factor, or component.
-
E.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05e4d48190864fc47bdffa4ca9 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.