Triple
T1927494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Rotor Volgograd |
E40864
|
entity |
| Predicate | participationPeakPeriod |
P3813
|
FINISHED |
| Object | 1990s European competitions |
—
|
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: 1990s European competitions | Statement: [FC Rotor Volgograd, participationPeakPeriod, 1990s European competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationPeakPeriod Context triple: [FC Rotor Volgograd, participationPeakPeriod, 1990s European competitions]
-
A.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
B.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
C.
circulationPeak
Indicates the highest level or maximum point reached in the circulation of something (such as money, media, or resources) within a given period or system.
-
D.
popularInPeriod
chosen
Indicates that something is widely liked, used, or influential during a specified time period.
-
E.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb263cdb8819084d0bda98a2a71e0 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.