Triple
T14786774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | surface fleet command staff |
E347546
|
entity |
| Predicate | typeOfForcesDirected |
P116102
|
FINISHED |
| Object | surface fleet |
—
|
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: surface fleet | Statement: [surface fleet command staff, typeOfForcesDirected, surface fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfForcesDirected Context triple: [surface fleet command staff, typeOfForcesDirected, surface fleet]
-
A.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
B.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
C.
natureOfForces
Indicates the fundamental type or character of the forces involved in an interaction or system.
-
D.
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.
-
E.
ledForcesFrom
Indicates that one entity commanded or directed military or armed forces originating from another entity or location.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa083e481908336d58d026eec32 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.