Triple
T31213197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain Hill, Arkansas, United States |
E795803
|
entity |
| Predicate | hasPatriarchBornHereOf |
P197450
|
FINISHED |
| Object | Jackson musical family |
—
|
NE NERFINISHED |
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: Jackson musical family | Statement: [Fountain Hill, Arkansas, United States, hasPatriarchBornHereOf, Jackson musical family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatriarchBornHereOf Context triple: [Fountain Hill, Arkansas, United States, hasPatriarchBornHereOf, Jackson musical family]
-
A.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
B.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
C.
hasCitizenBornHere
Indicates that a person holds citizenship in a place where they were also born.
-
D.
hasNotablePersonBornHere
Indicates that a notable or distinguished person was born at the referenced place.
-
E.
hasHometownOf
Indicates that one entity has, as its hometown, the place represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69fe9208ed708190980fb5061b22ae49 |
completed | May 9, 2026, 1:46 a.m. |
Created at: April 29, 2026, 9:09 p.m.