Triple
T17362675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engi |
E422106
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Enchō |
—
|
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: Enchō | Statement: [Engi, followedBy, Enchō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enchō Context triple: [Engi, followedBy, Enchō]
-
A.
Enchō
chosen
Enchō was a Japanese era name (nengō) of the early 10th century, used during the reign of Emperor Suzaku.
-
B.
Nishiizu
Nishiizu is a coastal town in Shizuoka Prefecture, Japan, known for its rugged seaside scenery, hot springs, and views of Suruga Bay.
-
C.
Enyō
Enyō is a minor Greek goddess associated with war, destruction, and the bloody chaos of battle, often depicted as a companion of Ares.
-
D.
Tenchō
Tenchō was a Japanese era name (nengō) of the early Heian period, used during the reign of Emperor Junna.
-
E.
Eikandō
Eikandō is a historic Buddhist temple in Kyoto, Japan, renowned for its autumn foliage and iconic statue of the Amida Buddha looking over its shoulder.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4e3c3481909dfaa00334c5010e |
completed | April 19, 2026, 2:13 a.m. |
Created at: April 10, 2026, 5:44 a.m.