Triple
T11237260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Heart is Inditing |
E265971
|
entity |
| Predicate | coronationAnthemNumber |
P98607
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [My Heart is Inditing, coronationAnthemNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationAnthemNumber Context triple: [My Heart is Inditing, coronationAnthemNumber, 4]
-
A.
coronationRight
Indicates the recognized right or entitlement of an entity to be crowned or to perform/receive a coronation.
-
B.
coronationEvent
Indicates the event in which a person is formally invested with royal authority and crowned as a monarch.
-
C.
coronationStatus
Indicates the current stage or condition of an entity’s coronation process, such as whether it is pending, ongoing, or completed.
-
D.
typicalCoronationOrder
Indicates the customary or standard sequence in which events or actions occur during a coronation ceremony.
-
E.
coCoronationWith
Indicates that two or more individuals were crowned or formally installed into their positions in the same coronation ceremony.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e904cf888190826fc964f76b5cb2 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:30 p.m.