Triple
T33110922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Leipzig |
E847328
|
entity |
| Predicate | majorityOfCrew |
P198657
|
FINISHED |
| Object | killed in action |
—
|
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: killed in action | Statement: [SMS Leipzig, majorityOfCrew, killed in action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorityOfCrew Context triple: [SMS Leipzig, majorityOfCrew, killed in action]
-
A.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
B.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
C.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
D.
totalCrewMembers
Indicates the total number of crew members associated with a given entity or context.
-
E.
missionRoleCrew-1
Indicates that a crew member participates in a mission in a specific operational role or capacity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_69fefa05757481908fa38f5c604afbbe |
completed | May 9, 2026, 9:10 a.m. |
Created at: May 1, 2026, 1:27 a.m.