Triple
T5491036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Vietnam Navy |
E123699
|
entity |
| Predicate | patrolled |
P21276
|
FINISHED |
| Object | Republic of Vietnam territorial waters |
—
|
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: Republic of Vietnam territorial waters | Statement: [Republic of Vietnam Navy, patrolled, Republic of Vietnam territorial waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patrolled Context triple: [Republic of Vietnam Navy, patrolled, Republic of Vietnam territorial waters]
-
A.
patrolledBy
chosen
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
B.
escortDuties
Indicates that one entity is responsible for accompanying and ensuring the safe or guided movement of another entity from one place or situation to another.
-
C.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
D.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
E.
sweep
Indicates that an agent uses a tool or motion to clear or move unwanted material from a surface or area.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927f198c8190889b555be9bf9765 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.