Triple
T34684746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank of the Helvetic Republic |
E890712
|
entity |
| Predicate | endUseApproxYear |
P82251
|
FINISHED |
| Object | early 1800s |
—
|
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: early 1800s | Statement: [Frank of the Helvetic Republic, endUseApproxYear, early 1800s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endUseApproxYear Context triple: [Frank of the Helvetic Republic, endUseApproxYear, early 1800s]
-
A.
endYearApprox
chosen
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
-
B.
approximateSettingYear
Indicates the approximate calendar year in which the primary events or setting of something (e.g., a work or scenario) take place.
-
C.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
-
D.
approximateDesignYear
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
-
E.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234cdb9c8190a6a46242de1b3926 |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.