Triple
T4986937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Glamorgan |
E112025
|
entity |
| Predicate | ceremonialRoleContinues |
P61326
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mid Glamorgan, ceremonialRoleContinues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialRoleContinues Context triple: [Mid Glamorgan, ceremonialRoleContinues, yes]
-
A.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
B.
ceremonialRoleInPeriod
Indicates that an entity holds or fulfills a specific ceremonial role during a defined time period.
-
C.
ceremonialStatus
Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
-
D.
ceremonialCycle
Indicates a recurring sequence of rituals or formal events that are performed in a set order over a defined period.
-
E.
ceremonialPowers
Indicates that an entity holds formal or symbolic authority associated with rituals or official ceremonies, without necessarily implying practical governing power.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd742311bc8190be016cac6cebd15d |
completed | March 20, 2026, 4:21 p.m. |
Created at: March 20, 2026, 1:34 p.m.