Triple
T12923475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlumberger |
E309180
|
entity |
| Predicate | hasEmployeeCount |
P17907
|
FINISHED |
| Object | over 80,000 employees |
—
|
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: over 80,000 employees | Statement: [Schlumberger, hasEmployeeCount, over 80,000 employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmployeeCount Context triple: [Schlumberger, hasEmployeeCount, over 80,000 employees]
-
A.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
-
B.
hasNumberOfCompanies
Indicates the quantitative relationship specifying how many companies are associated with a given entity.
-
C.
hasEmployeeRange
Indicates the range or limits on the number of employees associated with an entity.
-
D.
employsApproximateNumberOfPeople
chosen
Indicates that an entity employs a roughly estimated or approximate number of people, rather than an exact headcount.
-
E.
numberOfEmployeesDate
Indicates the specific date on which the recorded number of employees for an entity is valid or measured.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.