Triple
T1008059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Trench |
E21757
|
entity |
| Predicate | typeLocalityFor |
P9695
|
FINISHED |
| Object | Japan Trench subduction earthquakes |
—
|
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: Japan Trench subduction earthquakes | Statement: [Japan Trench, typeLocalityFor, Japan Trench subduction earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeLocalityFor Context triple: [Japan Trench, typeLocalityFor, Japan Trench subduction earthquakes]
-
A.
hasTypeLocality
chosen
Indicates the specific geographic location where an entity (typically a species or specimen) was originally found and formally described.
-
B.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
C.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
D.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
E.
addressLocality
Indicates the city, town, or locality in which an address is situated.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.