Triple
T10650327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kololo |
E250949
|
entity |
| Predicate | ruleEnded |
P14957
|
FINISHED |
| Object | circa 1864 |
—
|
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: circa 1864 | Statement: [Kololo, ruleEnded, circa 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleEnded Context triple: [Kololo, ruleEnded, circa 1864]
-
A.
endRule
chosen
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
B.
reasonForEndOfRule
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
C.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
D.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe4b97081908815b77612222318 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.