Triple
T34176142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝潮橋駅 |
E876676
|
entity |
| Predicate | ホーム構造 |
P50946
|
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.
domesticStructure
Indicates a structural or organizational relationship within a household or domestic setting, such as how roles, responsibilities, or living arrangements are arranged among its members.
-
B.
buildingStructure
chosen
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
roofStructures
Indicates a relationship where one entity consists of, includes, or is associated with roof-related structural elements of another entity.
-
D.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
E.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
- 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.