Triple
T30302597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS – Libya Province |
E770688
|
entity |
| Predicate | hasBranchOfOrigin |
P118109
|
FINISHED |
| Object | Islamic State of Iraq and the Levant |
—
|
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: Islamic State of Iraq and the Levant | Statement: [IS – Libya Province, hasBranchOfOrigin, Islamic State of Iraq and the Levant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchOfOrigin Context triple: [IS – Libya Province, hasBranchOfOrigin, Islamic State of Iraq and the Levant]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
establishedAsBranchBy
chosen
Indicates that one entity was created or designated as a branch or subsidiary by another entity.
-
D.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
E.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 7:49 p.m.