Triple
T33450240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinckney family |
E856617
|
entity |
| Predicate | earliestProminentGenerationCentury |
P178815
|
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: [Pinckney family, earliestProminentGenerationCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestProminentGenerationCentury Context triple: [Pinckney family, earliestProminentGenerationCentury, 18th century]
-
A.
earliestKnownGenerationCentury
chosen
Indicates the century in which the earliest known generation associated with an entity lived or is documented.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 1:37 a.m.