Triple
T172044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Majesty |
E3496
|
entity |
| Predicate | semanticType |
P7975
|
FINISHED |
| Object | third-person reference form |
—
|
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: third-person reference form | Statement: [Her Majesty, semanticType, third-person reference form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticType Context triple: [Her Majesty, semanticType, third-person reference form]
-
A.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
E.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a25a3ee6d08190a451ddba7504ce9b |
completed | Feb. 28, 2026, 3 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.