Triple
T22547918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regina Iohanna Secunda |
E557479
|
entity |
| Predicate | meaningOfComponent_Regina |
P62029
|
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: [Regina Iohanna Secunda, meaningOfComponent_Regina, queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfComponent_Regina Context triple: [Regina Iohanna Secunda, meaningOfComponent_Regina, queen]
-
A.
recognizedAsRegent
Indicates that an entity is formally acknowledged or designated as serving in the role of regent for another.
-
B.
meaningOfComponent R
chosen
Indicates that one entity represents the meaning, interpretation, or semantic content of another component.
-
C.
regentFor
Indicates that one entity serves as the ruling authority on behalf of another, typically during the latter’s minority, absence, or incapacity.
-
D.
genderOfRegent
Indicates the gender identity or classification of a regent in a governing or ruling role.
-
E.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f372df48190ae5dd461b1230bc7 |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.