Triple
T35503426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August von Heeringen |
E1026075
|
entity |
| Predicate | serviceNumberOfShipsUnderCommand |
P193742
|
FINISHED |
| Object | German U-boats in the Adriatic |
—
|
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: German U-boats in the Adriatic | Statement: [August von Heeringen, serviceNumberOfShipsUnderCommand, German U-boats in the Adriatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceNumberOfShipsUnderCommand Context triple: [August von Heeringen, serviceNumberOfShipsUnderCommand, German U-boats in the Adriatic]
-
A.
numberOfShips
Indicates the quantity of ships associated with a given entity or situation.
-
B.
otherShipsInFleet
Indicates that the subject ship and the object ship are distinct members of the same fleet.
-
C.
fleetConsistsOf
Indicates that a fleet is composed of, or includes as its members, the specified entities.
-
D.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
-
E.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:04 p.m.