Triple
T5951203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Oil Co. of New Jersey v. United States |
E132400
|
entity |
| Predicate | concernsIndustry |
P24922
|
FINISHED |
| Object | oil industry |
—
|
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: oil industry | Statement: [Standard Oil Co. of New Jersey v. United States, concernsIndustry, oil industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsIndustry Context triple: [Standard Oil Co. of New Jersey v. United States, concernsIndustry, oil industry]
-
A.
concernsBusinessType
Indicates that something is related or applicable to a particular type or category of business.
-
B.
industryContext
chosen
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
industryResponseTo
Indicates that an industry reacts or responds in some way to a particular event, condition, policy, or influence.
-
E.
economicSectorIssue
Indicates that there is a problem, challenge, or concern affecting a particular economic sector.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.