Triple
T140911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Torch |
E2846
|
entity |
| Predicate | navalComponent |
P4689
|
FINISHED |
| Object | Allied naval forces in the Western Mediterranean |
—
|
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: Allied naval forces in the Western Mediterranean | Statement: [Operation Torch, navalComponent, Allied naval forces in the Western Mediterranean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalComponent Context triple: [Operation Torch, navalComponent, Allied naval forces in the Western Mediterranean]
-
A.
navalFleet
chosen
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
B.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
C.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
-
D.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
E.
notableShip
Indicates that there is a notable or significant ship associated with the subject 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.