Triple
T27173326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Valdez |
E682975
|
entity |
| Predicate | placeScrapped |
P173352
|
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: [Exxon Valdez, placeScrapped, Alang, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeScrapped Context triple: [Exxon Valdez, placeScrapped, 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.
scrapedBy
Indicates that something has been obtained or collected from a source through a scraping process, typically by an automated tool or agent.
-
D.
scrappedAfter
Indicates that one entity was discarded, removed, or abandoned after another specified event or entity in time.
-
E.
scrappedAt
Indicates the time or date at which something was discarded, decommissioned, or removed from use.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 27, 2026, 9:24 a.m.