Triple
T9031687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapsi |
E216386
|
entity |
| Predicate | isPreparedOnOccasion |
P56481
|
FINISHED |
| Object | festivals |
—
|
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: festivals | Statement: [Lapsi, isPreparedOnOccasion, festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreparedOnOccasion Context triple: [Lapsi, isPreparedOnOccasion, festivals]
-
A.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
B.
isPreparedAs
Indicates that one entity is made ready, arranged, or configured in a particular way or form as specified by another entity.
-
C.
createdOnOccasionOf
chosen
Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
-
D.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
E.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6a9f2c7481909b4a272183f20585 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.