Triple
T25828250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurocentrism |
E650591
|
entity |
| Predicate | treatsAsUniversalNorm |
P12028
|
FINISHED |
| Object | European modernity |
—
|
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: European modernity | Statement: [Eurocentrism, treatsAsUniversalNorm, European modernity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsAsUniversalNorm Context triple: [Eurocentrism, treatsAsUniversalNorm, European modernity]
-
A.
normativeFor
chosen
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
isUniversal
Indicates that the relationship or property holds for all relevant entities or cases without exception.
-
C.
normativelyIncludes
Indicates that one norm or rule encompasses, subsumes, or otherwise includes another within its prescribed scope or requirements.
-
D.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
-
E.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 7:37 a.m.