Triple
T6262742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandrina |
E140338
|
entity |
| Predicate | hasFirstRecordedRoyalUse |
P39332
|
FINISHED |
| Object | 1819 |
—
|
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: 1819 | Statement: [Alexandrina, hasFirstRecordedRoyalUse, 1819]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstRecordedRoyalUse Context triple: [Alexandrina, hasFirstRecordedRoyalUse, 1819]
-
A.
firstCoronationHeldFor
Indicates that a particular entity was the subject or beneficiary of the first coronation event associated with another entity.
-
B.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
C.
startDateOfCurrentUseAsRoyalResidence
chosen
Indicates the date on which a place or building began its current period of use as a royal residence.
-
D.
hasCoronationRitual
Indicates that an entity is associated with a specific formal ceremony or set of rites used to crown or inaugurate a ruler or leader.
-
E.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06387fec0819095b47a37b9402aa9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.