Triple
T34400309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (1967) |
E882958
|
entity |
| Predicate | scrapyard |
P12194
|
FINISHED |
| Object | Alang, India |
—
|
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: Alang, India | Statement: [SS Empress of Britain (1967), scrapyard, Alang, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrapyard Context triple: [SS Empress of Britain (1967), scrapyard, Alang, India]
-
A.
scrappedTo
Indicates that something has been discarded, dismantled, or removed in order to be replaced or converted into another specified thing or state.
-
B.
scrapped
Indicates that something planned, created, or in progress was abandoned, discarded, or cancelled and will no longer be pursued or used.
-
C.
scrappedFrom
Indicates that something has been removed, discarded, or taken out of use from a particular source or context.
-
D.
scrappedAt
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
-
E.
soldForScrap
chosen
Indicates that something was disposed of or transferred specifically to be broken down and recycled for its material value rather than used in its original form.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:59 a.m.