Triple
T23108556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tate family of early settlers |
E576246
|
entity |
| Predicate | activeInTimePeriod |
P97182
|
FINISHED |
| Object | early settlement period of northern Mississippi |
—
|
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: early settlement period of northern Mississippi | Statement: [Tate family of early settlers, activeInTimePeriod, early settlement period of northern Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInTimePeriod Context triple: [Tate family of early settlers, activeInTimePeriod, early settlement period of northern Mississippi]
-
A.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
B.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
C.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
D.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
E.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0d3d4881908e32837b3fbbb406 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.