Triple
T4702928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Kakumanbuchi |
E104317
|
entity |
| Predicate | isInNationalContext |
P838
|
FINISHED |
| Object | inland lake of Japan |
—
|
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: inland lake of Japan | Statement: [Lake Kakumanbuchi, isInNationalContext, inland lake of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNationalContext Context triple: [Lake Kakumanbuchi, isInNationalContext, inland lake of Japan]
-
A.
hasCountryContext
chosen
Indicates that something is associated with, interpreted within, or relevant to a specific country or national context.
-
B.
representsInDomesticContext
Indicates that one entity serves as a representative or acts on behalf of another within a domestic or internal (non-international) context.
-
C.
hasNationalStatus
Indicates that an entity possesses an official national-level designation, recognition, or status within a country.
-
D.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
E.
isInGeopoliticalEntity
Indicates that one entity is located within, or is a part of, a specific geopolitical unit such as a country, state, or city.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.