Triple
T4266989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight-Eight Fleet Plan |
E96847
|
entity |
| Predicate | typeOfForcesPlanned |
P37308
|
FINISHED |
| Object | capital ships |
—
|
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: capital ships | Statement: [Eight-Eight Fleet Plan, typeOfForcesPlanned, capital ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfForcesPlanned Context triple: [Eight-Eight Fleet Plan, typeOfForcesPlanned, capital ships]
-
A.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
B.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
C.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
D.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
E.
includedForcesFrom
chosen
Indicates that one set of forces is derived from, or incorporated within, another set of forces.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.