Triple
T21105414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikoku Saburō |
E520027
|
entity |
| Predicate | hasNotableCityOnBanks |
P7935
|
FINISHED |
| Object | Tokushima |
—
|
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: Tokushima | Statement: [Shikoku Saburō, hasNotableCityOnBanks, Tokushima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCityOnBanks Context triple: [Shikoku Saburō, hasNotableCityOnBanks, Tokushima]
-
A.
hasNotableRiverPort
Indicates that a place possesses a river port recognized for its significance in transport, trade, or regional importance.
-
B.
hasCityOnRiver
Indicates that a city is located on or along the course of a particular river.
-
C.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
D.
hasCityOnBank
chosen
Indicates that a city is located on the bank of a particular river or body of water.
-
E.
hasNoLargeRiversFlowingIn
Indicates that the specified place does not have any major rivers flowing into it.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b6150f08190a3738f1eda7fa834 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.