Triple
T35448491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilman family |
E1024551
|
entity |
| Predicate | influentialCentury |
P56906
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Gilman family, influentialCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influentialCentury Context triple: [Gilman family, influentialCentury, 17th century]
-
A.
centuryOfGreatestInfluence
chosen
Indicates the century during which an entity exerted its greatest impact or influence.
-
B.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
C.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
D.
centuryCelebrated
Indicates that a particular century is being honored, commemorated, or formally celebrated in some way.
-
E.
collapseCentury
Indicates that one time period or event causes or undergoes a breakdown or compression of its century-level temporal distinction, effectively merging or reducing it into a different or broader timeframe.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:04 p.m.