Triple
T27004896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenrikyo |
E680215
|
entity |
| Predicate | originatedInPrefecture |
P185752
|
FINISHED |
| Object | Nara Prefecture |
—
|
NE NERFINISHED |
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: Nara Prefecture | Statement: [Tenrikyo, originatedInPrefecture, Nara Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedInPrefecture Context triple: [Tenrikyo, originatedInPrefecture, Nara Prefecture]
-
A.
locatedInRegionOfPrefecture
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
-
B.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
-
C.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
D.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
E.
isAssociatedWithPrefecture
chosen
Indicates that an entity has a connection or affiliation with a specific prefecture, such as administrative, geographic, or organizational association.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 27, 2026, 7 a.m.