Triple
T8955285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaza Seaport |
E213455
|
entity |
| Predicate | hasSecurityConstraint |
P22957
|
FINISHED |
| Object | naval patrols and restrictions |
—
|
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: naval patrols and restrictions | Statement: [Gaza Seaport, hasSecurityConstraint, naval patrols and restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityConstraint Context triple: [Gaza Seaport, hasSecurityConstraint, naval patrols and restrictions]
-
A.
hasAccessConstraint
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
-
B.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
-
C.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
-
E.
hasSecurityClass
Indicates that an entity is assigned to or associated with a particular security classification level.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6726cec48190a900ae52b1522adb |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.