Triple
T28984653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977–78 Biathlon World Cup |
E734644
|
entity |
| Predicate | circuitLevel |
P166266
|
FINISHED |
| Object | top-level |
—
|
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: top-level | Statement: [1977–78 Biathlon World Cup, circuitLevel, top-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitLevel Context triple: [1977–78 Biathlon World Cup, circuitLevel, top-level]
-
A.
circuitGrade
Indicates the quality or performance level assigned to a circuit, typically reflecting how well it meets specified standards or criteria.
-
B.
circuit
Indicates that one entity forms or participates in an electrical or logical pathway that allows current or signals to flow through a connected system involving another entity.
-
C.
circuitUsed
Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
-
D.
circuitType
Indicates the specific kind or category of electrical circuit associated with an entity.
-
E.
isCircuit
Indicates that an entity functions as or constitutes an electrical or logical circuit within a system.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:13 a.m.