Triple
T36338076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imam of the Ansar |
E894840
|
entity |
| Predicate | appliesToMovement |
P2459
|
FINISHED |
| Object | Ansar movement |
—
|
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: Ansar movement | Statement: [Imam of the Ansar, appliesToMovement, Ansar movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToMovement Context triple: [Imam of the Ansar, appliesToMovement, Ansar movement]
-
A.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
B.
basedOnMovement
Indicates that something is determined, derived, or decided according to the movement or motion of an entity.
-
C.
isMovement
Indicates that the subject undergoes or performs a change in position or location over time.
-
D.
includesMovementType
Indicates that one entity encompasses or contains a specific type or category of movement associated with another entity.
-
E.
associatedWithMovement
chosen
Indicates a relationship where an entity is connected to, involved in, or influenced by a particular movement (e.g., social, political, artistic, or ideological).
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:09 p.m.