Triple
T13987012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JNSY |
E336465
|
entity |
| Predicate | associatedForceType |
P1062
|
FINISHED |
| Object | 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: naval forces | Statement: [JNSY, associatedForceType, naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedForceType Context triple: [JNSY, associatedForceType, naval forces]
-
A.
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.
-
B.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
C.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
D.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
E.
supportsForce
Indicates that one entity provides the necessary structure, stability, or resistance to bear, counteract, or transmit a physical force exerted by another entity.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea537408190bb9d35963886803f |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.