Triple
T1113818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuckahoe marble |
E11050
|
entity |
| Predicate | typicalUsePeriodStart |
P4017
|
FINISHED |
| Object | early 19th century |
—
|
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 19th century | Statement: [Tuckahoe marble, typicalUsePeriodStart, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsePeriodStart Context triple: [Tuckahoe marble, typicalUsePeriodStart, early 19th century]
-
A.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
B.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
C.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.