Triple
T8200327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiji Basin |
E191552
|
entity |
| Predicate | isRegionOfInterestFor |
P24244
|
FINISHED |
| Object | earthquake studies |
—
|
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: earthquake studies | Statement: [Fiji Basin, isRegionOfInterestFor, earthquake studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionOfInterestFor Context triple: [Fiji Basin, isRegionOfInterestFor, earthquake studies]
-
A.
regionOfInterest
chosen
Indicates a specifically defined spatial or conceptual area that is selected for focused attention, analysis, or processing within a broader context.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
hasAreaOfInterest
Indicates that an entity possesses or is associated with a particular area of interest or focus.
-
D.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
E.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.