Triple
T13390988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln County, Kentucky |
E319570
|
entity |
| Predicate | createdWhen |
P7360
|
FINISHED |
| Object | Kentucky was part of Virginia |
—
|
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: Kentucky was part of Virginia | Statement: [Lincoln County, Kentucky, createdWhen, Kentucky was part of Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdWhen Context triple: [Lincoln County, Kentucky, createdWhen, Kentucky was part of Virginia]
-
A.
createdAt
chosen
Indicates the date and time at which an entity was initially created or came into existence.
-
B.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
C.
createdAtEvent
Indicates the specific event during which the entity was originally created.
-
D.
createdAtRequestOf
Indicates that something was created specifically in response to, or because of, a particular request.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d543348190a9c1be509b015c0f |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.