Triple
T19748561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Crowning ceremony |
E474315
|
entity |
| Predicate | oftenIncludesParticipants |
P2434
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [May Crowning ceremony, oftenIncludesParticipants, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenIncludesParticipants Context triple: [May Crowning ceremony, oftenIncludesParticipants, children]
-
A.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
B.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
C.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
D.
endedParticipationOf
Indicates that one entity caused or marked the termination of another entity’s involvement in an activity, event, or relationship.
-
E.
overseesParticipationOf
Indicates that one entity supervises, manages, or has authority over another entity’s involvement in an activity, process, or group.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.