Triple
T30867918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta-class submarine |
E786253
|
entity |
| Predicate | allianceReportingNameSystem |
P171102
|
FINISHED |
| Object | NATO reporting name system |
—
|
NE NERFINISHED |
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: NATO reporting name system | Statement: [Delta-class submarine, allianceReportingNameSystem, NATO reporting name system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceReportingNameSystem Context triple: [Delta-class submarine, allianceReportingNameSystem, NATO reporting name system]
-
A.
alliedReportingName
Indicates that an entity has a specific reporting name assigned by Allied forces for identification or reference.
-
B.
allianceName
Indicates the designated name or title assigned to an alliance between entities.
-
C.
allianceDesignationSystem
Indicates a system that defines, assigns, or manages formal alliance designations between entities.
-
D.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
-
E.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:47 p.m.