Triple
T26883863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Baptiste Tavernier |
E676985
|
entity |
| Predicate | broughtToEurope |
P17111
|
FINISHED |
| Object | French Blue diamond |
E172195
|
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: French Blue diamond | Statement: [Jean-Baptiste Tavernier, broughtToEurope, French Blue diamond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtToEurope Context triple: [Jean-Baptiste Tavernier, broughtToEurope, French Blue diamond]
-
A.
introducedToEuropeVia
Indicates that something was brought into and first became present in Europe through a particular source, route, or intermediary.
-
B.
broughtToBritainBy
Indicates that something or someone was transported or introduced into Britain by a particular agent or source.
-
C.
arrivalInEurope
chosen
Indicates the event or state of something or someone reaching or entering a location within Europe.
-
D.
introducedToEnglandBy
Indicates that one entity was responsible for bringing or first establishing another entity in England.
-
E.
introducedFromAmericasToOldWorld
Indicates that something originally from the Americas was brought and established in the Old World (Europe, Asia, or Africa) after trans-Atlantic contact.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1213692cb08190a608a3f4ce9982b8 |
completed | May 23, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 5:41 a.m.