Triple
T10834174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaspard |
E255704
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Jasper |
E268987
|
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: Jasper | Statement: [Gaspard, hasCognate, Jasper]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jasper Context triple: [Gaspard, hasCognate, Jasper]
-
A.
Jasper
Jasper is a cloud-based Internet of Things (IoT) platform company that provides tools for managing and monetizing connected devices and services.
-
B.
Jasper
Jasper is a surname of English origin borne by various individuals, including Margaret Jasper.
-
C.
Jasper
Jasper is a small city in northwestern Alabama known historically for its coal mining and role in the state's industrial development.
-
D.
Jasper
chosen
Jasper is a masculine given name of Persian origin meaning "treasurer," historically associated with one of the Three Wise Men and used in various English-speaking countries.
-
E.
Jasper
Jasper is a small city located in Jasper County in the southwestern part of the U.S. state of Missouri.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d74425447081908fb51c7edf54af67 |
completed | April 9, 2026, 6:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb11a264c8190829ff89f0b13d063 |
completed | April 14, 2026, 9:26 p.m. |
Created at: April 8, 2026, 9:19 p.m.