Triple
T3703167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bush |
E80827
|
entity |
| Predicate | hasBusinessInvolvement |
P21206
|
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: [Bush, hasBusinessInvolvement, oil industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessInvolvement Context triple: [Bush, hasBusinessInvolvement, oil industry]
-
A.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
B.
hasMemberInvolvedIn
Indicates that a group or collective entity has at least one of its members participating in or engaged with a specified activity, event, or situation.
-
C.
hasBusiness
chosen
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
D.
formerlyInvolved
Indicates that an entity previously participated in or was associated with another entity or activity, but is no longer involved.
-
E.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54925b48190b23d2a14ef825abc |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:33 p.m.