Triple
T37119657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taffy 3 |
E919210
|
entity |
| Predicate | facingForceType |
P116102
|
FINISHED |
| Object | Japanese battleships, cruisers, and destroyers |
—
|
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: Japanese battleships, cruisers, and destroyers | Statement: [Taffy 3, facingForceType, Japanese battleships, cruisers, and destroyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facingForceType Context triple: [Taffy 3, facingForceType, Japanese battleships, cruisers, and destroyers]
-
A.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
B.
typeOfForcesDirected
chosen
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
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.
axisForce
Indicates a force applied along a specific axis or direction between entities.
-
E.
axisForcesStrength
Indicates the magnitude or intensity of forces acting along a specified axis.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.