Triple
T2841072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancroft |
E62467
|
entity |
| Predicate | hasNotableHistoricalPeriod |
P4928
|
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: [Sancroft, hasNotableHistoricalPeriod, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHistoricalPeriod Context triple: [Sancroft, hasNotableHistoricalPeriod, 17th century]
-
A.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
-
B.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
C.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
D.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
E.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.