Triple
T31952485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS St. Louis (CL-49) |
E815816
|
entity |
| Predicate | scrappedApproxDate |
P16228
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [USS St. Louis (CL-49), scrappedApproxDate, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrappedApproxDate Context triple: [USS St. Louis (CL-49), scrappedApproxDate, 1970s]
-
A.
scrappedAt
chosen
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
-
B.
scrappedAfter
Indicates that one entity was discarded, removed, or abandoned after another specified event or entity in time.
-
C.
scrappedTo
Indicates that something has been discarded, dismantled, or removed in order to be replaced or converted into another specified thing or state.
-
D.
scrappedUnder
Indicates that one entity has been discarded, abandoned, or removed from use or consideration under the authority, conditions, or context defined by another entity.
-
E.
scrapped
Indicates that something planned, created, or in progress was abandoned, discarded, or cancelled and will no longer be pursued or used.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2ac9bd481909a1e8adb4e294262 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.