Triple
T30281671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spencer-Stanhope |
E770109
|
entity |
| Predicate | historicallyActiveInCentury |
P1560
|
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: [Spencer-Stanhope, historicallyActiveInCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyActiveInCentury Context triple: [Spencer-Stanhope, historicallyActiveInCentury, 18th century]
-
A.
activeInCentury
chosen
Indicates that an entity was active, influential, or operational during a specified century.
-
B.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
C.
happenedInCentury
Indicates that an event or occurrence took place during a specified century.
-
D.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
E.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: April 29, 2026, 7:45 p.m.