Triple
T27434663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motomachi-Chukagai Station |
E690744
|
entity |
| Predicate | hasSubname |
P37539
|
FINISHED |
| Object | Motomachi-Chukagai Station (Yamashita-koen) |
—
|
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: Motomachi-Chukagai Station (Yamashita-koen) | Statement: [Motomachi-Chukagai Station, hasSubname, Motomachi-Chukagai Station (Yamashita-koen)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubname Context triple: [Motomachi-Chukagai Station, hasSubname, Motomachi-Chukagai Station (Yamashita-koen)]
-
A.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
B.
hasSubdomain
Indicates that one domain is a subordinate or nested part of another domain within a hierarchical naming structure.
-
C.
hasSubNamespace
Indicates that one namespace is a direct subordinate or contained namespace within another namespace.
-
D.
hasSubAppellation
chosen
Indicates that one appellation (name or title) is a more specific or subordinate form of another appellation.
-
E.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 12:43 p.m.