Triple
T1016542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Royal Highness |
E21941
|
entity |
| Predicate | formalRegister |
P4035
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [His Royal Highness, formalRegister, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalRegister Context triple: [His Royal Highness, formalRegister, yes]
-
A.
formalFunction
Indicates that an entity serves an official or designated role or purpose within a formal structure, system, or context.
-
B.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
C.
formalityLevel
chosen
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
-
D.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
E.
formalContent
Indicates that the content is expressed in a formal, structured, or official manner, as opposed to casual or informal expression.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c1e9d08190baf7e81f3777168d |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.