Triple
T38675621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Philippine Sea |
E943730
|
entity |
| Predicate | officialNameInPhilippines |
P86937
|
FINISHED |
| Object | West Philippine Sea |
—
|
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: West Philippine Sea | Statement: [West Philippine Sea, officialNameInPhilippines, West Philippine Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameInPhilippines Context triple: [West Philippine Sea, officialNameInPhilippines, West Philippine Sea]
-
A.
hasOfficialNameInFilipino
Indicates that an entity has an official or formally recognized name expressed in the Filipino language.
-
B.
philippineName
Indicates that an entity has a name used in the Philippine context, such as in Filipino or other Philippine languages.
-
C.
officialNameLocal
chosen
Indicates the officially recognized name of an entity as used in the local or native language context.
-
D.
officialName
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
-
E.
officialNameInSpanish
Indicates the officially recognized name of an entity when expressed in the Spanish language.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:33 p.m.