Triple
T33514277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Harra |
E858323
|
entity |
| Predicate | associatedEventSideB |
P206498
|
FINISHED |
| Object | inhabitants of Medina |
—
|
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: inhabitants of Medina | Statement: [al-Harra, associatedEventSideB, inhabitants of Medina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEventSideB Context triple: [al-Harra, associatedEventSideB, inhabitants of Medina]
-
A.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
B.
associatedFair
Indicates a relationship where one entity is linked or connected to a particular fair, such as being held at, organized by, or otherwise related to that fair.
-
C.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
-
D.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
E.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:39 a.m.