Triple
T26033797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamas 2017 political document |
E647499
|
entity |
| Predicate | placeAnnounced |
P3059
|
FINISHED |
| Object | Doha |
—
|
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: Doha | Statement: [Hamas 2017 political document, placeAnnounced, Doha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeAnnounced Context triple: [Hamas 2017 political document, placeAnnounced, Doha]
-
A.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
B.
announcementLocation
chosen
Indicates the place or venue where an announcement is made or presented.
-
C.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
D.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
E.
announcedThrough
Indicates that an announcement or communication was made via a particular medium, channel, or intermediary.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 9:06 a.m.