Triple
T24224220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Pipe |
E601545
|
entity |
| Predicate | hasNotableTraineeType |
P155259
|
FINISHED |
| Object | champion hurdlers |
—
|
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: champion hurdlers | Statement: [Martin Pipe, hasNotableTraineeType, champion hurdlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTraineeType Context triple: [Martin Pipe, hasNotableTraineeType, champion hurdlers]
-
A.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
B.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
C.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
D.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
E.
hasNotableTeamType
Indicates that an entity is associated with a team that is recognized as having a specific notable type or category.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287ddfecc81909f5396857974bc8c |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, midnight