Triple
T29468219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pad 1/5 |
E747437
|
entity |
| Predicate | launchedPerson |
P171814
|
FINISHED |
| Object | Yuri Gagarin |
—
|
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: Yuri Gagarin | Statement: [Pad 1/5, launchedPerson, Yuri Gagarin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedPerson Context triple: [Pad 1/5, launchedPerson, Yuri Gagarin]
-
A.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
-
B.
hasPerson
Indicates that an entity is associated with or includes a specific person.
-
C.
documentedPerson
Indicates that a person is the subject of documentation or records in some source or system.
-
D.
namedIndividual
Indicates that the subject is a specific, uniquely identified individual entity rather than a general class or type.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 3:55 p.m.