Triple
T37829034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | río Pastaza |
E943144
|
entity |
| Predicate | tipoDeCurso |
P189256
|
FINISHED |
| Object | río andino-amazónico |
—
|
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: río andino-amazónico | Statement: [río Pastaza, tipoDeCurso, río andino-amazónico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeCurso Context triple: [río Pastaza, tipoDeCurso, río andino-amazónico]
-
A.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
B.
curriculumType
Indicates the classification or category of curriculum associated with an educational program or course.
-
C.
typicalCourse
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
-
D.
isCourse
Indicates that an entity functions as or qualifies as a course within a given context or system.
-
E.
notableCourseType
Indicates that a course has a particular notable or distinguished type or classification (e.g., flagship, honors, or otherwise specially recognized).
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.