Triple
T37979708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trail of Broken Treaties caravan |
E947518
|
entity |
| Predicate | hasDemandsDocument |
P142847
|
FINISHED |
| Object | Twenty-Point Position Paper |
—
|
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: Twenty-Point Position Paper | Statement: [Trail of Broken Treaties caravan, hasDemandsDocument, Twenty-Point Position Paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemandsDocument Context triple: [Trail of Broken Treaties caravan, hasDemandsDocument, Twenty-Point Position Paper]
-
A.
requiresDocument
Indicates that one entity can only proceed, be valid, or be completed if a specified document is provided or present.
-
B.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
C.
hasDOC
chosen
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
D.
hasNotableDocument
Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
-
E.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:20 p.m.