Triple
T22283913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Lara |
E550808
|
entity |
| Predicate | testDebut |
P147685
|
FINISHED |
| Object | 1990-12-06 |
—
|
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: 1990-12-06 | Statement: [Brian Lara, testDebut, 1990-12-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testDebut Context triple: [Brian Lara, testDebut, 1990-12-06]
-
A.
testDebutFor
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
B.
testDebutAgainst
Indicates that an entity’s first test appearance or performance occurs in opposition to, or is evaluated against, a specified counterpart or context.
-
C.
testDebutVenue
Indicates the venue or location where an entity (such as a person, product, or performance) made its first test appearance or trial debut.
-
D.
isDebut
Indicates that something is the first formal appearance or introduction of an entity, such as a person, work, or performance, in a particular context or domain.
-
E.
testDebutForCountry
Indicates the event in which an individual makes their first official test appearance representing a particular country.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15605a8448190906a0ab9ffa4260b |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.