Triple
T34883096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Timkat |
E1006065
|
entity |
| Predicate | evePractice |
P181970
|
FINISHED |
| Object | procession of tabot to water |
—
|
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: procession of tabot to water | Statement: [Feast of Timkat, evePractice, procession of tabot to water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evePractice Context triple: [Feast of Timkat, evePractice, procession of tabot to water]
-
A.
practicedWith
Indicates that one entity engaged in practice or training together with another entity.
-
B.
practicedFor
Indicates that an entity engaged in preparation or rehearsal directed toward a particular event, activity, or objective.
-
C.
practicedUnder
Indicates that one entity gained experience or training while working under the guidance, supervision, or mentorship of another entity.
-
D.
alsoPractice
Indicates that an entity engages in the same practice or activity as another entity, in addition to any other practices it may have.
-
E.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.