Triple
T27173341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Shipping Co. v. Baker |
E682976
|
entity |
| Predicate | aroseFromDate |
P124706
|
FINISHED |
| Object | March 24, 1989 |
—
|
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: March 24, 1989 | Statement: [Exxon Shipping Co. v. Baker, aroseFromDate, March 24, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aroseFromDate Context triple: [Exxon Shipping Co. v. Baker, aroseFromDate, March 24, 1989]
-
A.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
-
B.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
C.
raisedOn
Indicates that an entity was nurtured, brought up, or spent its formative period in a particular place, environment, or context.
-
D.
originatedAround
chosen
Indicates that something began, emerged, or came into existence approximately at a specified time or within a loosely defined period.
-
E.
initiatedBecauseOf
Indicates that one event, action, or process was started as a direct result of, or in response to, another specified cause or condition.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62549039c8190af7159d07416c985 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:24 a.m.