Triple
T18520638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wartime emergency administration |
E452572
|
entity |
| Predicate | typicallyEndsWith |
P7167
|
FINISHED |
| Object | cessation of hostilities |
—
|
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: cessation of hostilities | Statement: [wartime emergency administration, typicallyEndsWith, cessation of hostilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyEndsWith Context triple: [wartime emergency administration, typicallyEndsWith, cessation of hostilities]
-
A.
blendsWith
Indicates that one entity can be mixed or combined smoothly with another to form a uniform or harmonious result.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
endsWith
chosen
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other entity.
-
D.
nameEnding
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
E.
endsUpWith
Indicates that, as a result of some process or sequence of events, one entity ultimately comes to possess, receive, or be associated with 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338db5e4819086503a2176dfe499 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.