Triple
T19849213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caramelo |
E476949
|
entity |
| Predicate | hasAuthorHeritage |
P77479
|
FINISHED |
| Object | Mexican American |
—
|
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: Mexican American | Statement: [Caramelo, hasAuthorHeritage, Mexican American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorHeritage Context triple: [Caramelo, hasAuthorHeritage, Mexican American]
-
A.
hasAuthorCulturalIdentity
chosen
Indicates that an author is associated with a particular cultural identity or background.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
D.
hasAuthorBackgroundIn
Indicates that an author possesses a particular background, such as education, experience, or expertise, in a specified field or domain.
-
E.
hasTypeOfHeritage
Indicates that an entity is associated with a specific category or classification of heritage (such as cultural, natural, or historical heritage).
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658664368819082783bc40342a26a |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.