Triple
T1553882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Estates of Scotland |
E33155
|
entity |
| Predicate | nobleComponent |
P9679
|
FINISHED |
| Object | lords temporal |
—
|
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: lords temporal | Statement: [Three Estates of Scotland, nobleComponent, lords temporal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleComponent Context triple: [Three Estates of Scotland, nobleComponent, lords temporal]
-
A.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
B.
sovereignComponent
Indicates that one entity functions as a constituent part of a larger sovereign whole, such as a state, polity, or authority.
-
C.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
D.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
E.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.