Triple
T6741063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loko |
E154081
|
entity |
| Predicate | foundedAsLokomotivYaroslavl |
P364
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Loko, foundedAsLokomotivYaroslavl, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsLokomotivYaroslavl Context triple: [Loko, foundedAsLokomotivYaroslavl, 1959]
-
A.
foundedAsIceHockeyLeagueOf
Indicates that an entity was originally established in the role or form of an ice hockey league for another entity.
-
B.
foundedAsAHLFranchise
Indicates that an organization or team was originally established as a franchise in the American Hockey League (AHL).
-
C.
foundedAsRepresentativeTeam
Indicates that an entity was established specifically to serve as a representative team for a larger group, organization, or region.
-
D.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
foundedAsTeam
Indicates that an organization or club was originally established in the form of a team.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18971e081908372cd25d52a11bd |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.