Triple
T26033810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamas 2017 political document |
E647499
|
entity |
| Predicate | acceptsStateOn |
P159889
|
FINISHED |
| Object | 1967 borders |
—
|
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: 1967 borders | Statement: [Hamas 2017 political document, acceptsStateOn, 1967 borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsStateOn Context triple: [Hamas 2017 political document, acceptsStateOn, 1967 borders]
-
A.
laterAccepts
Indicates that one entity accepts, approves, or agrees to something at a time subsequent to a referenced earlier point or event.
-
B.
acceptingStatesSymbol
Indicates that a given symbol is associated with one or more accepting (final) states in an automaton or state-transition system.
-
C.
admittedState
Indicates that an entity has been formally accepted or allowed into a particular state or condition.
-
D.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
E.
receivingState
Indicates that one entity serves as the recipient or destination of something (such as an object, message, or person) from another entity.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061bfb248190af47ba49de93abfc |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 9:06 a.m.