Triple
T6443976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdullah al-Janabi |
E138294
|
entity |
| Predicate | notableRoleLocation |
P70680
|
FINISHED |
| Object | mosques in Fallujah |
—
|
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: mosques in Fallujah | Statement: [Abdullah al-Janabi, notableRoleLocation, mosques in Fallujah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRoleLocation Context triple: [Abdullah al-Janabi, notableRoleLocation, mosques in Fallujah]
-
A.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
D.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
E.
notableCityOfOperation
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698c17ec81909f6bbcbe636a67fd |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.