Triple
T20461753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criollo |
E501939
|
entity |
| Predicate | sociallyRankedAbove |
P60246
|
FINISHED |
| Object | mestizos |
—
|
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: mestizos | Statement: [Criollo, sociallyRankedAbove, mestizos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sociallyRankedAbove Context triple: [Criollo, sociallyRankedAbove, mestizos]
-
A.
rankedAmong
Indicates that an entity holds a specific position or status within a defined group, list, or hierarchy of comparable entities.
-
B.
sharesRankWith
Indicates that two entities have the same rank or hierarchical level within a given ordering or classification.
-
C.
socialPosition
chosen
Indicates the relative social status, rank, or standing one entity holds within a social hierarchy or structure in relation to others.
-
D.
sociallyIntegratedWith
Indicates that two entities are connected through meaningful social relationships, interactions, or participation within the same social context or community.
-
E.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a642648190808709020f91122b |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.