Triple
T1011150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival of Nine Lessons and Carols |
E21825
|
entity |
| Predicate | hasStructureElement |
P3097
|
FINISHED |
| Object | bidding prayer |
—
|
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: bidding prayer | Statement: [Festival of Nine Lessons and Carols, hasStructureElement, bidding prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureElement Context triple: [Festival of Nine Lessons and Carols, hasStructureElement, bidding prayer]
-
A.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
C.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
-
D.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
E.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.