Triple
T31086347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuga Island |
E792248
|
entity |
| Predicate | strategicLocationIn |
P2850
|
FINISHED |
| Object | Luzon Strait |
—
|
NE NERFINISHED |
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: Luzon Strait | Statement: [Fuga Island, strategicLocationIn, Luzon Strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicLocationIn Context triple: [Fuga Island, strategicLocationIn, Luzon Strait]
-
A.
strategicLocation
chosen
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:02 p.m.