Triple
T38675661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Coast Guard |
E943731
|
entity |
| Predicate | canDetainVessels |
P162171
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chinese Coast Guard, canDetainVessels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDetainVessels Context triple: [Chinese Coast Guard, canDetainVessels, yes]
-
A.
isInterdictionVessel
chosen
Indicates that the vessel is designated or used for interdiction operations, such as stopping, boarding, or inspecting other vessels.
-
B.
isVesselFor
Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
-
C.
nationalityOfVessels
Indicates the country or flag state to which vessels legally belong or are registered.
-
D.
marineProtectionStatus
Indicates the level or type of legal or regulatory protection applied to a marine area or resource.
-
E.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.