Triple
T21519966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 都筑郡 |
E530945
|
entity |
| Predicate | 関連地形 |
P87992
|
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.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
D.
topographicallyContrastedWith
Indicates that two geographic areas are compared or distinguished based on differences in their physical surface features or terrain.
-
E.
adjacentLandform
Indicates that two landforms are directly next to each other in space, sharing a common boundary or lying in immediate proximity.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884af0f08190bc1f3d70e57a325d |
completed | April 26, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.