Triple
T34245706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benioff zone |
E878590
|
entity |
| Predicate | notedExample |
P32479
|
FINISHED |
| Object | Japan subduction zones |
—
|
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 subduction zones | Statement: [Benioff zone, notedExample, Japan subduction zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notedExample Context triple: [Benioff zone, notedExample, Japan subduction zones]
-
A.
notableExampleAt
chosen
Indicates that something serves as a prominent or illustrative example of something else in a particular context or location.
-
B.
notableExampleBy
Indicates that something serves as a prominent or illustrative example provided or created by a particular entity.
-
C.
usedAsExampleIn
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
D.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
E.
notableDemo
Indicates that an entity is particularly well known or recognized for a specific demonstration, example, or showcase.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.