Triple
T7002664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Ploughing Ceremony |
E162373
|
entity |
| Predicate | dateFormat |
P73533
|
FINISHED |
| Object | set by royal astrologers |
—
|
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: set by royal astrologers | Statement: [Royal Ploughing Ceremony, dateFormat, set by royal astrologers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFormat Context triple: [Royal Ploughing Ceremony, dateFormat, set by royal astrologers]
-
A.
dateNotation
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
B.
formatAfter
Indicates that one entity’s format or structural arrangement is derived from, follows, or is applied subsequent to another entity’s format.
-
C.
dateFormedFrom
Indicates that one date value is derived or constructed from another date or date-related source.
-
D.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
E.
formatBefore
Indicates that one item’s format or formatting must occur or be applied prior to another item’s format or formatting.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc1115c48190a9363473ae21b6c1 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.