Triple
T26883816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tavernier Blue |
E676984
|
entity |
| Predicate | firstKnownDocumentationDate |
P138680
|
FINISHED |
| Object | 1670s |
—
|
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: 1670s | Statement: [Tavernier Blue, firstKnownDocumentationDate, 1670s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownDocumentationDate Context triple: [Tavernier Blue, firstKnownDocumentationDate, 1670s]
-
A.
earliestDocumentsDate
chosen
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
B.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
C.
firstDocumentedBy
Indicates that one entity is the person or source that originally recorded, reported, or documented the other entity for the first time.
-
D.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
E.
firstClearlyRecognizedIn
Indicates the point in time or context when something was first clearly identified, acknowledged, or distinguished as such.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: April 27, 2026, 5:41 a.m.