Triple
T2038731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Equipment Corporation |
E44692
|
entity |
| Predicate | employeeCountAtPeak |
P17907
|
FINISHED |
| Object | over 100000 |
—
|
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 100000 | Statement: [Digital Equipment Corporation, employeeCountAtPeak, over 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employeeCountAtPeak Context triple: [Digital Equipment Corporation, employeeCountAtPeak, over 100000]
-
A.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
B.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
-
C.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
D.
employsApproximateNumberOfPeople
chosen
Indicates that an entity employs a roughly estimated or approximate number of people, rather than an exact headcount.
-
E.
staffSize
Indicates the number of staff members associated with an entity.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb951870481909dbdd8fc8b0c02fe |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.