Triple
T38042465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Samuel B. Roberts (FFG-58) |
E949525
|
entity |
| Predicate | resultOfMining |
P195755
|
FINISHED |
| Object | severe hull and engineering damage |
—
|
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: severe hull and engineering damage | Statement: [USS Samuel B. Roberts (FFG-58), resultOfMining, severe hull and engineering damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfMining Context triple: [USS Samuel B. Roberts (FFG-58), resultOfMining, severe hull and engineering damage]
-
A.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
isMinedIn
Indicates that a resource or material is extracted or obtained from a particular location or site.
-
C.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
D.
minedUnder
Indicates that one entity is extracted or mined from beneath the surface or structural level of another entity.
-
E.
minerRepresents
Indicates that a miner acts on behalf of, or serves as a representative or proxy for, another entity in a given context.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:20 p.m.