Triple
T30208622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordine Toscano |
E768005
|
entity |
| Predicate | isMonarchical |
P8695
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ordine Toscano, isMonarchical, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonarchical Context triple: [Ordine Toscano, isMonarchical, true]
-
A.
isMonarchicalStyle
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
-
B.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
C.
monarchyStatus
chosen
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
D.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
E.
traditionalMonarchy
Indicates a system where a monarchy operates according to long-established customs, hereditary succession, and historical institutions rather than modern or codified reforms.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67fca43448190b108c8c1b998738f |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.