Triple
T4092081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Žalgiris |
E87725
|
entity |
| Predicate | hasPredecessorEra |
P3444
|
FINISHED |
| Object | Soviet Union basketball era |
—
|
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: Soviet Union basketball era | Statement: [BC Žalgiris, hasPredecessorEra, Soviet Union basketball era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredecessorEra Context triple: [BC Žalgiris, hasPredecessorEra, Soviet Union basketball era]
-
A.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
B.
hasHistoricalPrecursor
chosen
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
C.
previousEraNameDerivedFrom
Indicates that the name of the current era is derived from, or based on, the name of a preceding era.
-
D.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
-
E.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.