Triple
T9689013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kannon |
E234489
|
entity |
| Predicate | centralToPractice |
P4751
|
FINISHED |
| Object | Kannon devotion |
—
|
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: Kannon devotion | Statement: [Kannon, centralToPractice, Kannon devotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToPractice Context triple: [Kannon, centralToPractice, Kannon devotion]
-
A.
primaryPractice
Indicates that one entity is the main or most significant activity, occupation, or method regularly carried out or used by another entity.
-
B.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
practicedMedicineIn
Indicates that a person engaged in the professional practice of medicine within a specified location or jurisdiction.
-
D.
regionOfPractice
Indicates the geographic area or jurisdiction in which an entity regularly conducts its professional activities or services.
-
E.
modernPractice
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d019d40819095059a4d6167900a |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.