Triple
T38261645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 Prague |
E1017942
|
entity |
| Predicate | usesGamifiedCurriculum |
P10895
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [42 Prague, usesGamifiedCurriculum, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGamifiedCurriculum Context triple: [42 Prague, usesGamifiedCurriculum, yes]
-
A.
usesCurriculum
chosen
Indicates that one entity adopts or applies a particular curriculum as the basis for its instruction, training, or educational activities.
-
B.
usesLearningPlatform
Indicates that an entity makes use of a particular learning platform for educational or training purposes.
-
C.
hasCurriculumGoal
Indicates that an educational curriculum includes or is associated with a specific intended learning goal or objective.
-
D.
usesCourse
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
-
E.
usesEnrollment
Indicates that one entity employs or relies on a particular enrollment record, process, or status in order to function or be applied.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.