Triple
T23544839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Darter |
E577861
|
entity |
| Predicate | attemptedDestructionBy |
P122917
|
FINISHED |
| Object | USS Dace |
—
|
NE NERFINISHED |
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: USS Dace | Statement: [USS Darter, attemptedDestructionBy, USS Dace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedDestructionBy Context triple: [USS Darter, attemptedDestructionBy, USS Dace]
-
A.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
C.
demolitionAttempts
chosen
Indicates attempts made to demolish or destroy a target object, structure, or entity.
-
D.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
E.
attemptedToKill
Indicates that one entity took deliberate action with the intention of causing the death of another entity, regardless of whether the death actually occurred.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1ef55c8190a93c33e704ec3b5a |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.