Triple
T17300965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weatherford International |
E420036
|
entity |
| Predicate | completedRestructuring |
P1574
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Weatherford International, completedRestructuring, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedRestructuring Context triple: [Weatherford International, completedRestructuring, 2019]
-
A.
wasRestructuredInto
Indicates that an entity underwent an organizational or structural change resulting in it becoming a different, successor entity.
-
B.
hadDivisionalRestructuring
Indicates that an entity has undergone a reorganization of its internal divisions or business units.
-
C.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
E.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fae8848190a06c5866e606baac |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.