Triple
T32199843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I in Persia |
E822500
|
entity |
| Predicate | hasRelatedAgreement |
P145119
|
FINISHED |
| Object | Anglo-Russian Convention of 1907 |
E169739
|
NE 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: Anglo-Russian Convention of 1907 | Statement: [World War I in Persia, hasRelatedAgreement, Anglo-Russian Convention of 1907]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedAgreement Context triple: [World War I in Persia, hasRelatedAgreement, Anglo-Russian Convention of 1907]
-
A.
hasTypeOfAgreement
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
B.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
hasCustomerAgreement
Indicates that a customer is bound by or associated with a specific agreement or contract.
-
D.
formedByAgreementWith
chosen
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
E.
hasAgreementSystem
Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
- F. None of above.
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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0befa324819080d66941b2ec9235 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
Created at: May 1, 2026, 12:36 a.m.