Triple
T3267606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabrini–Green |
E68563
|
entity |
| Predicate | numberOfResidentsAtPeak |
P6809
|
FINISHED |
| Object | over 15000 |
—
|
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 15000 | Statement: [Cabrini–Green, numberOfResidentsAtPeak, over 15000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfResidentsAtPeak Context triple: [Cabrini–Green, numberOfResidentsAtPeak, over 15000]
-
A.
populationAtPeak
chosen
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
B.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
C.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
D.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
-
E.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafcf9c6c819092f9c618b778b46d |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.