Triple
T2489734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Exeter |
E52009
|
entity |
| Predicate | navalTreatyContext |
P21293
|
FINISHED |
| Object | Washington Naval Treaty cruiser |
—
|
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: Washington Naval Treaty cruiser | Statement: [HMS Exeter, navalTreatyContext, Washington Naval Treaty cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTreatyContext Context triple: [HMS Exeter, navalTreatyContext, Washington Naval Treaty cruiser]
-
A.
navalTreatyCategory
chosen
Indicates that something is classified under a specific category or type within the context of naval treaties.
-
B.
treatyFocus
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
-
C.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
D.
navalPolicy
Indicates the policies, strategies, or regulatory stance a state or authority adopts regarding the organization, deployment, and use of its naval forces.
-
E.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd17b7a048190bcc8f0a66514a052 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.