Triple
T172054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Majesty |
E3496
|
entity |
| Predicate | belongsToSystem |
P840
|
FINISHED |
| Object | monarchical forms of address |
—
|
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: monarchical forms of address | Statement: [Her Majesty, belongsToSystem, monarchical forms of address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSystem Context triple: [Her Majesty, belongsToSystem, monarchical forms of address]
-
A.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
E.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25a3f9d188190aacf5791273e2c65 |
completed | Feb. 28, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69a25667717c8190bac5108366e2178d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.