Triple
T36199071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prim's minimum spanning tree algorithm |
E1047207
|
entity |
| Predicate | originallyDiscoveredBy |
P412
|
FINISHED |
| Object | Vojtěch Jarník |
E1681009
|
NE 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: Vojtěch Jarník | Statement: [Prim's minimum spanning tree algorithm, originallyDiscoveredBy, Vojtěch Jarník]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyDiscoveredBy Context triple: [Prim's minimum spanning tree algorithm, originallyDiscoveredBy, Vojtěch Jarník]
-
A.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
B.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
C.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
-
D.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
E.
eponymOfDiscovererOf
Indicates that one entity gives its name to the person who discovered another entity.
- F. None of above.
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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39341b50048190b4a595da536fa1de |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.