Triple
T37449054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Trade Center Health Registry |
E930628
|
entity |
| Predicate | estimatedEnrollment |
P30984
|
FINISHED |
| Object | 71000 |
—
|
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: 71000 | Statement: [World Trade Center Health Registry, estimatedEnrollment, 71000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedEnrollment Context triple: [World Trade Center Health Registry, estimatedEnrollment, 71000]
-
A.
hasApproximateStudents
chosen
Indicates that an entity is associated with an estimated or approximate number of students, rather than an exact count.
-
B.
typicalEnrollment
Indicates the usual or standard number of participants or members enrolled in something, such as a course, program, or institution.
-
C.
enrollmentSize
Indicates the number of individuals enrolled or registered in a particular group, program, or institution.
-
D.
undergraduateEnrollment
Indicates the number of undergraduate students enrolled in an institution or program.
-
E.
enrollment
Indicates the formal act of registering or being registered in a course, program, or institution, establishing an official participant–provider relationship.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.