Triple
T16755558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Naval Conference |
E407197
|
entity |
| Predicate | navalRatioAgreed |
P124518
|
FINISHED |
| Object | 5:5:3:1.67:1.67 |
—
|
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: 5:5:3:1.67:1.67 | Statement: [Washington Naval Conference, navalRatioAgreed, 5:5:3:1.67:1.67]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalRatioAgreed Context triple: [Washington Naval Conference, navalRatioAgreed, 5:5:3:1.67:1.67]
-
A.
navalRating
Indicates the assessed level of naval strength, capability, or performance attributed to an entity.
-
B.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
C.
navalPolicy
Indicates the policies, strategies, or regulatory stance a state or authority adopts regarding the organization, deployment, and use of its naval forces.
-
D.
navalTreatyCategory
Indicates that something is classified under a specific category or type within the context of naval treaties.
-
E.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe831ec8190bac05b07db6153c1 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.