Triple
T24213212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of SF Hydro |
E600611
|
entity |
| Predicate | carriedFor |
P155226
|
FINISHED |
| Object | German nuclear program |
—
|
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: German nuclear program | Statement: [sinking of SF Hydro, carriedFor, German nuclear program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedFor Context triple: [sinking of SF Hydro, carriedFor, German nuclear program]
-
A.
carriedFrom
Indicates that something was transported or moved away starting from a specified source location or origin.
-
B.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
C.
carriedSince
Indicates that one entity has been continuously carrying or transporting another entity starting from a specified point in time.
-
D.
carriedOver
Indicates that something from a previous context, state, or period is transferred and remains applicable or in effect in the current one.
-
E.
carriedProp
Indicates that one entity transported or bore another entity as a carried object or property.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28204e288819081e8a6121e229df6 |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:56 p.m.