Triple
T18997658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Corona |
E464860
|
entity |
| Predicate | positionOnMilitaryCrown |
P134069
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [De Corona, positionOnMilitaryCrown, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnMilitaryCrown Context triple: [De Corona, positionOnMilitaryCrown, critical]
-
A.
crownPosition
Indicates the relative placement or orientation of a crown with respect to another object or reference point.
-
B.
positionInRegalia
Indicates the specific role or rank an individual holds within a formal regalia or ceremonial order.
-
C.
positionDuringCoronation
Indicates the specific role, title, or office an entity held at the time of a coronation event.
-
D.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
E.
crownRepresents
Indicates that one entity (the crown) symbolically stands for, embodies, or serves as an official emblem of another entity, such as authority, sovereignty, or a governing body.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6826464819080ff0e0ffa5cc25e |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.