Triple
T27418235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōgaki |
E692962
|
entity |
| Predicate | formedNewCity |
P115274
|
FINISHED |
| Object | Etajima |
—
|
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: Etajima | Statement: [Ōgaki, formedNewCity, Etajima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNewCity Context triple: [Ōgaki, formedNewCity, Etajima]
-
A.
builtCityWhere
Indicates that an agent constructed or established a city at the specified location.
-
B.
newMunicipalityName
Indicates that an entity has been assigned or is associated with a newly designated municipality name.
-
C.
buildCity
chosen
Indicates the action of constructing or establishing a city at a particular location or within a certain context.
-
D.
addsCity
Indicates that an entity incorporates or appends a city to a collection, list, or structure.
-
E.
developedAsCityDueTo
Indicates that a settlement or area became a city specifically as a result of the influence, presence, or development of the referenced cause or factor.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 12:35 p.m.