Triple
T31625541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tawwabin uprising |
E807012
|
entity |
| Predicate | hasInitialRallyPoint |
P181727
|
FINISHED |
| Object | Kufa |
—
|
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: Kufa | Statement: [Tawwabin uprising, hasInitialRallyPoint, Kufa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitialRallyPoint Context triple: [Tawwabin uprising, hasInitialRallyPoint, Kufa]
-
A.
hasInitialPointMonument
Indicates that a monument serves as the designated initial or starting point for a referenced spatial feature or boundary.
-
B.
hasStartLandmark
chosen
Indicates that an entity begins, originates, or is initially located at a specified landmark.
-
C.
hasTrailAccessPoint
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
D.
hasStartingArea
Indicates that an entity is associated with, or begins from, a specific initial area or region.
-
E.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: April 30, 2026, 10:43 p.m.