Triple
T3134498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarborough Shoal |
E65494
|
entity |
| Predicate | hasNearbyWatersUsedBy |
P45574
|
FINISHED |
| Object | Philippine fishers |
—
|
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: Philippine fishers | Statement: [Scarborough Shoal, hasNearbyWatersUsedBy, Philippine fishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWatersUsedBy Context triple: [Scarborough Shoal, hasNearbyWatersUsedBy, Philippine fishers]
-
A.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
B.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
C.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
D.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
E.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:05 p.m.