Triple
T27154683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schieffelin family |
E682487
|
entity |
| Predicate | historicalActivityPeriod |
P58089
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Schieffelin family, historicalActivityPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalActivityPeriod Context triple: [Schieffelin family, historicalActivityPeriod, 18th century]
-
A.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
B.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
-
C.
shareHistoricalUnionPeriod
Indicates that two entities were part of the same political or administrative union during an overlapping historical time period.
-
D.
historicalActivation
Indicates that an entity was active or in effect during a specific historical period or past timeframe.
-
E.
historicalRangeIncludes
Indicates that the temporal span or period associated with one entity encompasses the historical time range of another entity.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 9:16 a.m.