Triple
T1455006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid Conference of 1991 |
E31377
|
entity |
| Predicate | includedDelegation |
P12024
|
FINISHED |
| Object | Israeli delegation |
—
|
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: Israeli delegation | Statement: [Madrid Conference of 1991, includedDelegation, Israeli delegation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedDelegation Context triple: [Madrid Conference of 1991, includedDelegation, Israeli delegation]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
canDelegateTo
Indicates that one entity has the authority or ability to transfer or assign its responsibilities, tasks, or decision-making power to another entity.
-
C.
includesOrganization
chosen
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
-
D.
includesInvitedTeams
Indicates that certain teams are explicitly included as invited participants in an event, activity, or context.
-
E.
includedLeader
Indicates that an entity is recognized or designated as a leader within a specified group, set, or collection.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57fead881909a47188ce7312406 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.