Triple
T1733076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Institute of Technology Radiation Laboratory |
E37856
|
entity |
| Predicate | numberOfStaffAtPeak |
P24266
|
FINISHED |
| Object | approximately 4000 |
—
|
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: approximately 4000 | Statement: [Massachusetts Institute of Technology Radiation Laboratory, numberOfStaffAtPeak, approximately 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStaffAtPeak Context triple: [Massachusetts Institute of Technology Radiation Laboratory, numberOfStaffAtPeak, approximately 4000]
-
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.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
C.
staffSize
Indicates the number of staff members associated with an entity.
-
D.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
-
E.
personnelStrength
chosen
Indicates the number or capacity of people assigned to or available for a particular unit, organization, or operation.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.