Triple
T9457393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Roe (DD-418) |
E228051
|
entity |
| Predicate | hasNATOCategory |
P72828
|
FINISHED |
| Object | surface combatant |
—
|
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: surface combatant | Statement: [USS Roe (DD-418), hasNATOCategory, surface combatant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNATOCategory Context triple: [USS Roe (DD-418), hasNATOCategory, surface combatant]
-
A.
hasNATOContext
Indicates that something is related to, influenced by, or situated within the context of NATO, its activities, policies, or structures.
-
B.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
C.
NATOCategory
chosen
Indicates that an entity is classified according to a specific NATO-defined category or designation.
-
D.
hasNATOCompatibleSystems
Indicates that an entity possesses systems or equipment that are compatible with NATO standards and can interoperate with NATO forces.
-
E.
NATOClassification
Indicates the formal security or information classification level assigned under NATO standards to an item, document, or communication.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f90cf648190ab238ba6b4f03c4f |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.