Triple
T224339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinto |
E4281
|
entity |
| Predicate | historicalPractice |
P9816
|
FINISHED |
| Object | shinbutsu shūgō |
—
|
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: shinbutsu shūgō | Statement: [Shinto, historicalPractice, shinbutsu shūgō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPractice Context triple: [Shinto, historicalPractice, shinbutsu shūgō]
-
A.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
C.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dea93b48190863a3704b233aa03 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.