Triple
T27263118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vallenato |
E687821
|
entity |
| Predicate | notOriginallyFrom |
P77572
|
FINISHED |
| Object | Paisa region of Colombia |
—
|
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: Paisa region of Colombia | Statement: [Vallenato, notOriginallyFrom, Paisa region of Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOriginallyFrom Context triple: [Vallenato, notOriginallyFrom, Paisa region of Colombia]
-
A.
notNativeTo
chosen
Indicates that an entity does not originate from, or is not naturally occurring in, a specified place or environment.
-
B.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
C.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
-
D.
hasNotabilityOrigin
Indicates that an entity’s notability or prominence arises from, or is primarily associated with, a specified origin (such as a place, context, or source).
-
E.
notDerivedFrom
Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626f07218819080448c001f01ba45 |
completed | May 2, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:54 a.m.