Triple
T37652256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terecô |
E937203
|
entity |
| Predicate | hasRitualTime |
P194450
|
FINISHED |
| Object | night ceremonies |
—
|
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: night ceremonies | Statement: [Terecô, hasRitualTime, night ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualTime Context triple: [Terecô, hasRitualTime, night ceremonies]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
hasRitualStage
Indicates that something is associated with, or occurs during, a particular stage within a ritual process.
-
C.
hasRitualSequence
Indicates that one ritual is ordered to occur before or after another within a defined ceremonial sequence.
-
D.
hasRitualSetting
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
-
E.
hasRitualDay
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:18 p.m.