Triple
T31485710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippines–United States border |
E803269
|
entity |
| Predicate | primarilyAdjacentToTerritoriesOf |
P181353
|
FINISHED |
| Object | Guam |
E544
|
NE 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: Guam | Statement: [Philippines–United States border, primarilyAdjacentToTerritoriesOf, Guam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarilyAdjacentToTerritoriesOf Context triple: [Philippines–United States border, primarilyAdjacentToTerritoriesOf, Guam]
-
A.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
B.
borderingCountryOfTerritory
Indicates that one country shares a land or maritime boundary with the specified territory.
-
C.
affectsTerritoryOf
Indicates that one entity causes changes to, or has an impact on, the territorial domain or jurisdiction of another entity.
-
D.
geographicallyBorders
chosen
Indicates that two geographic entities share a common boundary or border.
-
E.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
- F. None of above.
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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b5627dae88190a3d082c228bb232a |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:35 p.m.