Triple
T31746336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VICTORIA REGINA ET IMPERATRIX |
E810279
|
entity |
| Predicate | ReginaMeaning |
P64447
|
FINISHED |
| Object | Queen |
—
|
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: Queen | Statement: [VICTORIA REGINA ET IMPERATRIX, ReginaMeaning, Queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ReginaMeaning Context triple: [VICTORIA REGINA ET IMPERATRIX, ReginaMeaning, Queen]
-
A.
regnalNameMeaning
Indicates that a regnal name has a particular meaning, explaining what that official ruling name signifies or translates to.
-
B.
meaningOfRegnalName
chosen
Indicates the relationship in which a regnal name signifies or denotes its specific meaning or interpretation.
-
C.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
D.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
E.
namingMeaning
Indicates that one entity provides the meaning, sense, or semantic interpretation of a given name or naming expression for another entity.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab4db95c819083ff04ad3069881b |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:26 p.m.