Triple
T36369703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Area Maritime Surveillance |
E895719
|
entity |
| Predicate | surveillanceArea |
P185171
|
FINISHED |
| Object | open ocean |
—
|
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: open ocean | Statement: [Broad Area Maritime Surveillance, surveillanceArea, open ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceArea Context triple: [Broad Area Maritime Surveillance, surveillanceArea, open ocean]
-
A.
surveillanceCondition
Indicates the specific circumstances or criteria under which surveillance or monitoring of an entity is required, active, or applicable.
-
B.
protectsArea
Indicates that one entity serves to guard, defend, or preserve a particular area or region from harm or intrusion.
-
C.
surveillanceMeans
Indicates that one entity is used as a method, tool, or channel through which surveillance or monitoring of another entity is carried out.
-
D.
surveillanceStrengthenedDuring
Indicates that surveillance measures were intensified or reinforced during a specified time period or event.
-
E.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
- F. None of above. chosen
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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bb3f23f48190b0b9c2d667e09b52 |
completed | May 3, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.