Triple
T30033192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yema |
E763078
|
entity |
| Predicate | selectionOrTraining |
P83637
|
FINISHED |
| Object | apprenticeship under senior Yema |
—
|
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: apprenticeship under senior Yema | Statement: [Yema, selectionOrTraining, apprenticeship under senior Yema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionOrTraining Context triple: [Yema, selectionOrTraining, apprenticeship under senior Yema]
-
A.
trainingAfterSelection
Indicates that a training activity occurs after a selection process has taken place.
-
B.
trainingIn
Indicates that one entity is undergoing or receiving training within the context, program, or domain specified by another entity.
-
C.
trainingUnder
chosen
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
D.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
E.
selectionDescribedIn
Indicates that a particular selection or choice is documented, explained, or detailed within a specified description or source.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:50 p.m.