Triple
T15077682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipscomb County |
E380047
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Follett |
E401392
|
NE 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: Follett | Statement: [Lipscomb County, hasMunicipality, Follett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Follett Context triple: [Lipscomb County, hasMunicipality, Follett]
-
A.
Follett
chosen
Follett is a surname most prominently associated with British author Ken Follett, known for his bestselling historical and thriller novels.
-
B.
Faulks
Faulks is the surname of British novelist and journalist Sebastian Faulks, best known for his historical and literary fiction.
-
C.
Rinehart
Rinehart is a small unincorporated community located in the U.S. state of Missouri.
-
D.
Brenan
Brenan is a given name and surname that serves as a spelling variant of Brennen.
-
E.
Figes
Figes is a surname most notably associated with British historian and author Orlando Figes, known for his works on Russian and European history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fe5a208190823900b25e298dab |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5d4f6a48190aeb42341b0c395a7 |
completed | May 9, 2026, 3:11 a.m. |
Created at: April 10, 2026, 3:03 a.m.