Triple
T35881726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Savage Sr. |
E1037525
|
entity |
| Predicate | designedTrainingFor |
P40765
|
FINISHED |
| Object | Doc Savage |
—
|
NE NERFINISHED |
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: Doc Savage | Statement: [Clark Savage Sr., designedTrainingFor, Doc Savage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedTrainingFor Context triple: [Clark Savage Sr., designedTrainingFor, Doc Savage]
-
A.
providesTrainingFor
chosen
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
B.
trainingIn
Indicates that one entity is undergoing or receiving training within the context, program, or domain specified by another entity.
-
C.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
-
D.
trainedAccordingTo
Indicates that an entity has been trained or instructed in alignment with a specified method, standard, guideline, or curriculum.
-
E.
alsoTrains
Indicates that an entity, in addition to its primary role or activity, is involved in training 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:06 p.m.