Triple
T29118538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Defence Act 1910 |
E737111
|
entity |
| Predicate | typeOfForceCreated |
P138231
|
FINISHED |
| Object | permanent naval forces |
—
|
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: permanent naval forces | Statement: [Naval Defence Act 1910, typeOfForceCreated, permanent naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfForceCreated Context triple: [Naval Defence Act 1910, typeOfForceCreated, permanent naval forces]
-
A.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
B.
hasTypeOfForces
chosen
Indicates that one entity is associated with, or characterized by, a particular kind or category of forces.
-
C.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
D.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
E.
generatesForce
Indicates that one entity produces or exerts a physical force on another entity or on its surroundings.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: April 28, 2026, 11:24 a.m.