Triple
T1460265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Left |
E31494
|
entity |
| Predicate | hasDemographicBase |
P7875
|
FINISHED |
| Object | 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: students | Statement: [New Left, hasDemographicBase, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemographicBase Context triple: [New Left, hasDemographicBase, students]
-
A.
hasDemographic
chosen
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
B.
hasDemographicCenter
Indicates that an entity has a primary geographic location where the majority or core concentration of its associated population or demographic group is found.
-
C.
demographics
Indicates the relationship of providing or characterizing statistical information about a population’s attributes, such as age, gender, income, or education.
-
D.
demographicsSource
Indicates the origin or provider from which demographic information about an entity is obtained.
-
E.
demographicsDescriptor
Indicates a descriptive attribute or classification that characterizes the demographic properties of an entity or group.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.