Triple
T34176030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | おおさかしみなとく |
E876673
|
entity |
| Predicate | 区名の由来 |
P24038
|
FINISHED |
| Object | 港湾機能を持つ「港」に由来する |
—
|
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: 港湾機能を持つ「港」に由来する | Statement: [おおさかしみなとく, 区名の由来, 港湾機能を持つ「港」に由来する]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 区名の由来 Context triple: [おおさかしみなとく, 区名の由来, 港湾機能を持つ「港」に由来する]
-
A.
districtNameOrigin
chosen
Indicates that the relationship specifies the origin or source from which a district’s name is derived.
-
B.
historicalRegionNameDerivedFrom
Indicates that the name of a historical region is derived from, or based on, the name of another entity (such as a place, people, or feature).
-
C.
valleyNameDerivedFrom
Indicates that the name of a valley is derived from, or based on, another specified source (such as a person, place, language term, or feature).
-
D.
islandNameDerivedFrom
Indicates that the name of an island is derived from, based on, or taken from another specified source.
-
E.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe9fc488190b55b7cf618473fc6 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.