Triple
T17303123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schelling’s middle to late period |
E420087
|
entity |
| Predicate | timePeriodApproximateStart |
P48368
|
FINISHED |
| Object | around 1809 |
—
|
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: around 1809 | Statement: [Schelling’s middle to late period, timePeriodApproximateStart, around 1809]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodApproximateStart Context triple: [Schelling’s middle to late period, timePeriodApproximateStart, around 1809]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
timePeriodApproximation
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
D.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fc732481909065afddc5c687d4 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.