Triple
T13749494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGE |
E330303
|
entity |
| Predicate | stanceOnRace |
P110828
|
FINISHED |
| Object | centers Black people as original people |
—
|
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: centers Black people as original people | Statement: [NGE, stanceOnRace, centers Black people as original people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnRace Context triple: [NGE, stanceOnRace, centers Black people as original people]
-
A.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
B.
stanceOnSegregation
Indicates a person or group’s expressed position, attitude, or viewpoint regarding racial or social segregation.
-
C.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing event.
-
D.
stanceOnAuthority
Indicates an entity’s attitude, position, or level of support or opposition toward authority or authoritative control.
-
E.
racePolicy
Indicates that an entity has established rules, practices, or guidelines governing how races or competitive events are conducted or managed.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02148c208190a882927905a861a6 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:08 p.m.