Triple
T11708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triumphant Democracy |
E239
|
entity |
| Predicate | comparesWith |
P278
|
FINISHED |
| Object | British system of government |
—
|
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: British system of government | Statement: [Triumphant Democracy, comparesWith, British system of government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesWith Context triple: [Triumphant Democracy, comparesWith, British system of government]
-
A.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
C.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
D.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
E.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a241ea1ea081908e8a81ca97531ba5 |
completed | Feb. 28, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69a23fe7da8c8190aea795b62cb91621 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.