Triple
T1967815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ship Security Assessment |
E42728
|
entity |
| Predicate | documentedAs |
P519
|
FINISHED |
| Object | confidential security information |
—
|
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: confidential security information | Statement: [Ship Security Assessment, documentedAs, confidential security information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedAs Context triple: [Ship Security Assessment, documentedAs, confidential security information]
-
A.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
D.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
-
E.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cf15048190a51f73ed85e1b958 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.