Triple
T2800956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovefeast |
E53151
|
entity |
| Predicate | canBeHeldOn |
P36317
|
FINISHED |
| Object | special occasions |
—
|
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: special occasions | Statement: [Lovefeast, canBeHeldOn, special occasions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHeldOn Context triple: [Lovefeast, canBeHeldOn, special occasions]
-
A.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
B.
areHeldIn
chosen
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
C.
canBring
Indicates that one entity has the ability or permission to bring another entity or item to a particular place or context.
-
D.
canBeHeldEarly
Indicates that an event, action, or process is allowed to occur earlier than its originally scheduled or typical time.
-
E.
automaticallyHeld
Indicates that the holding or possession relationship occurs by default or system rule, without requiring an explicit action or decision by the involved entities.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.