Triple
T37449053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Trade Center Health Registry |
E930628
|
entity |
| Predicate | cohortType |
P187827
|
FINISHED |
| Object | closed cohort |
—
|
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: closed cohort | Statement: [World Trade Center Health Registry, cohortType, closed cohort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cohortType Context triple: [World Trade Center Health Registry, cohortType, closed cohort]
-
A.
cohortBased
Indicates that entities are grouped or treated together based on belonging to the same cohort (e.g., time-based or batch-based grouping).
-
B.
cohortStructure
Indicates the organizational relationship that defines how a cohort is structured or grouped into its constituent parts.
-
C.
numberOfCohorts
Indicates the total count of distinct cohorts associated with or involved in a given entity or context.
-
D.
enrollmentType
Indicates the specific category or mode under which an entity is enrolled in a program, service, or system.
-
E.
relatedCohort
Indicates that two or more entities are associated through membership in, or connection to, the same cohort or grouped population.
- F. None of above. chosen
Provenance (4 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.