Triple
T23007979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claiborne, Alabama |
E572829
|
entity |
| Predicate | wasIncorporated |
P48685
|
FINISHED |
| Object | early 19th 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: early 19th century | Statement: [Claiborne, Alabama, wasIncorporated, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIncorporated Context triple: [Claiborne, Alabama, wasIncorporated, early 19th century]
-
A.
laterIncorporated
Indicates that one entity was formally established, merged, or integrated as a legal or organizational body at a later time than another entity or reference point.
-
B.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
D.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
E.
eraOfEstablishment
chosen
Indicates the time period or historical era during which an entity was founded or established.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835802a881908fe817c3fa728a82 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.