Triple
T28561954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coron Island |
E722569
|
entity |
| Predicate | bestKnownPeriod |
P164640
|
FINISHED |
| Object | World War II wreck diving |
—
|
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: World War II wreck diving | Statement: [Coron Island, bestKnownPeriod, World War II wreck diving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestKnownPeriod Context triple: [Coron Island, bestKnownPeriod, World War II wreck diving]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
C.
strongestPeriodUnder
Indicates that one entity represents the time period during which another entity exhibits its maximum or strongest value, effect, or performance.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
- F. None of above. chosen
Provenance (4 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f650542a1c8190b6f0e66be3bba62c |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 4:05 a.m.