Triple
T19313718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southside neighborhood |
E483038
|
entity |
| Predicate | typicalResident |
P41733
|
FINISHED |
| Object | university students |
—
|
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: university students | Statement: [Southside neighborhood, typicalResident, university students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResident Context triple: [Southside neighborhood, typicalResident, university students]
-
A.
typicalProfile
chosen
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
E.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cf25c081908a30814b15d78c25 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.