Triple
T21020253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somers Mutiny |
E517785
|
entity |
| Predicate | executionsConductedWithout |
P87565
|
FINISHED |
| Object | court-martial |
—
|
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: court-martial | Statement: [Somers Mutiny, executionsConductedWithout, court-martial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionsConductedWithout Context triple: [Somers Mutiny, executionsConductedWithout, court-martial]
-
A.
operatedWithout
chosen
Indicates that an action, process, or entity functioned or was carried out in the absence of a specified resource, condition, or participant.
-
B.
launchesConductedFor
Indicates that one entity performs or carries out launches on behalf of, or for the benefit of, another entity.
-
C.
ceasedOperationsDuring
Indicates that an entity stopped functioning or carrying out its activities at some point within the specified time period.
-
D.
noShotsFired
Indicates that in the referenced situation or interaction, no gunshots or firearm discharges occurred.
-
E.
launchesConducted
Indicates that one entity has carried out or executed one or more launch events involving another entity or object.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5c905c8190ba2f9f82b6cd1648 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.