Triple
T16838874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | geiko |
E409352
|
entity |
| Predicate | requiresTrainingPeriod |
P118093
|
FINISHED |
| Object | several years |
—
|
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: several years | Statement: [geiko, requiresTrainingPeriod, several years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTrainingPeriod Context triple: [geiko, requiresTrainingPeriod, several years]
-
A.
requiresTraining
Indicates that one entity can only be properly or legitimately used, performed, or engaged with if the other entity has first received appropriate training.
-
B.
requiresTrainingAt
Indicates that one entity must undergo or complete training at a specified organization, institution, or location as a prerequisite or requirement.
-
C.
trainingPeriod
chosen
Indicates the duration or phase during which training or instruction is formally conducted.
-
D.
includesTrainingPhase
Indicates that something contains or encompasses a specific training phase as part of its overall process or structure.
-
E.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34ed7d48190a5f8d9f03a332a22 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.