Triple
T12459111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isonokami Shrine |
E297741
|
entity |
| Predicate | formerShrineRankSystem |
P71066
|
FINISHED |
| Object | Modern system of ranked Shinto shrines |
—
|
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: Modern system of ranked Shinto shrines | Statement: [Isonokami Shrine, formerShrineRankSystem, Modern system of ranked Shinto shrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerShrineRankSystem Context triple: [Isonokami Shrine, formerShrineRankSystem, Modern system of ranked Shinto shrines]
-
A.
shrineRank
Indicates the hierarchical or status level assigned to a shrine relative to other shrines.
-
B.
formerRankingSystem
chosen
Indicates that a ranking system previously used in a given context is no longer current or in effect.
-
C.
formerRanking
Indicates that an entity previously held a particular rank or position but no longer does so.
-
D.
formerSpireStatus
Indicates that an entity previously held a particular status or role within a spire but no longer does.
-
E.
shrineType
Indicates the specific category or kind of shrine associated with an 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.