Triple
T3105236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Machiavel |
E64814
|
entity |
| Predicate | positionOnRulership |
P16871
|
FINISHED |
| Object | advocates moral rulership |
—
|
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: advocates moral rulership | Statement: [Anti-Machiavel, positionOnRulership, advocates moral rulership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnRulership Context triple: [Anti-Machiavel, positionOnRulership, advocates moral rulership]
-
A.
positionOnMonarchy
chosen
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
B.
roleInKingship
Indicates that an entity holds or plays a specific role or position within a system of kingship or royal authority.
-
C.
positionOnStateRole
Indicates that an entity holds or occupies a specific role or position within a governmental or state-related organizational structure.
-
D.
positionDuringCoronation
Indicates the specific role, title, or office an entity held at the time of a coronation event.
-
E.
positionOnCentralization
Indicates the degree to which an entity favors centralized versus decentralized control, authority, or decision-making.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29a90e88190afb8a10291ef1946 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.