Triple
T15070351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Versailles arms limitations |
E379858
|
entity |
| Predicate | limitedTorpedoBoatsTo |
P117201
|
FINISHED |
| Object | 12 torpedo boats |
—
|
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: 12 torpedo boats | Statement: [Versailles arms limitations, limitedTorpedoBoatsTo, 12 torpedo boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedTorpedoBoatsTo Context triple: [Versailles arms limitations, limitedTorpedoBoatsTo, 12 torpedo boats]
-
A.
missileTubesPerBoat
Indicates the number of missile tubes associated with each individual boat in the relationship.
-
B.
numberOfTorpedoTubes
Indicates the quantity of torpedo tubes associated with or installed on an entity.
-
C.
torpedoCaliber
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
D.
numberOfMissileTubes
Indicates the quantity of missile tubes that an entity possesses or is equipped with.
-
E.
antiTorpedoProtection
Indicates a defensive relationship where measures are in place to protect against or mitigate the effects of torpedo attacks.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7f86df48190b3a2cf441fefb477 |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:02 a.m.