Triple
T33070102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hon Tre |
E846210
|
entity |
| Predicate | isPartOfCountryMaritimeArea |
P166112
|
FINISHED |
| Object | Vietnamese 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: Vietnamese waters | Statement: [Hon Tre, isPartOfCountryMaritimeArea, Vietnamese waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCountryMaritimeArea Context triple: [Hon Tre, isPartOfCountryMaritimeArea, Vietnamese waters]
-
A.
isMaritimeRegion
Indicates that a region is primarily associated with the sea or ocean, such as being coastal, oceanic, or otherwise defined by maritime characteristics or activities.
-
B.
isPartOfMaritimeZone
chosen
Indicates that one area or feature is contained within, or legally belongs to, a specified maritime zone.
-
C.
isPartOfCoastOf
Indicates that one entity forms a segment or component of the coastline belonging to another entity.
-
D.
borderingSeaAreaOf
Indicates that one entity is a sea area that directly borders or adjoins the coastline or maritime boundary of another entity.
-
E.
hasTerritorialSeaIn
Indicates that an entity’s territorial sea is located within or extends into the area or jurisdiction 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 1, 2026, 1:25 a.m.