Triple
T9736648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub-Lieutenant (Royal Naval Reserve) |
E236079
|
entity |
| Predicate | NATOOFCode |
P6062
|
FINISHED |
| Object | OF-1 |
—
|
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: OF-1 | Statement: [Sub-Lieutenant (Royal Naval Reserve), NATOOFCode, OF-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOOFCode Context triple: [Sub-Lieutenant (Royal Naval Reserve), NATOOFCode, OF-1]
-
A.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
hasNATOContext
Indicates that something is related to, influenced by, or situated within the context of NATO, its activities, policies, or structures.
-
C.
positionOnNATO
Indicates a country's stance or alignment regarding membership in, support for, or opposition to NATO.
-
D.
NOC
Indicates a relationship where one entity is not permitted, not compatible, or otherwise not allowed to occur or coexist with another entity.
-
E.
NATOCategory
Indicates that an entity is classified according to a specific NATO-defined category or designation.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef032088190acd94c35b89e48b7 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.