Triple
T15261174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altior |
E364777
|
entity |
| Predicate | debutOverHurdlesIn |
P100535
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Altior, debutOverHurdlesIn, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debutOverHurdlesIn Context triple: [Altior, debutOverHurdlesIn, 2014]
-
A.
madeProfessionalDebutIn
Indicates the time or event in which an individual first performed or appeared in a professional capacity within a given field or organization.
-
B.
debuted
chosen
Indicates that an entity made its first public appearance, performance, or introduction at a particular time or place.
-
C.
debutResult
Indicates the outcome or performance result associated with an entity’s first formal appearance or introduction (its debut).
-
D.
debutedWith
Indicates that an entity made its first public appearance, release, or introduction in association with another specified entity.
-
E.
madeCollegiateDebut
Indicates that an individual participated in their first official competition or appearance at the collegiate level.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084e85a08190b8e63598b9f6a535 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.