Triple
T32275873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Dragon |
E824543
|
entity |
| Predicate | NATO pennant number |
P3153
|
FINISHED |
| Object | D35 |
—
|
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: D35 | Statement: [HMS Dragon, NATO pennant number, D35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATO pennant number Context triple: [HMS Dragon, NATO pennant number, D35]
-
A.
pennantNumber
chosen
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
B.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
C.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
-
D.
isDistinctiveUnitInsignia
Indicates that one entity serves as the distinctive unit insignia (a unique identifying emblem or badge) associated with another entity, typically a military unit.
-
E.
associatedWithNATO
Indicates a relationship in which an entity has a formal or recognized connection, affiliation, or involvement with NATO.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.