Triple
T34769962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. BP Exploration & Production Inc. |
E1002336
|
entity |
| Predicate | arisesFromDate |
P181824
|
FINISHED |
| Object | 2010-04-20 |
—
|
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: 2010-04-20 | Statement: [United States v. BP Exploration & Production Inc., arisesFromDate, 2010-04-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arisesFromDate Context triple: [United States v. BP Exploration & Production Inc., arisesFromDate, 2010-04-20]
-
A.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
B.
originatedAround
Indicates that something began, emerged, or came into existence approximately at a specified time or within a loosely defined period.
-
C.
mayDateFrom
Indicates that one entity is permitted or allowed to go on a date with another entity.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
arisesIn
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.