Triple
T14072504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuskaloosa |
E338644
|
entity |
| Predicate | uncertainDetails |
P9778
|
FINISHED |
| Object | exact birth date unknown |
—
|
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: exact birth date unknown | Statement: [Tuskaloosa, uncertainDetails, exact birth date unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uncertainDetails Context triple: [Tuskaloosa, uncertainDetails, exact birth date unknown]
-
A.
hasUncertainNature
Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
-
B.
hasUncertainIdentification
Indicates that the identification or classification of an entity in the relationship is doubtful, ambiguous, or not fully confirmed.
-
C.
hasUncertainNumber
Indicates that the associated quantity or count is not known precisely or cannot be determined with certainty.
-
D.
hasUncertainty
chosen
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
E.
notGuaranteed
Indicates that the specified outcome, condition, or obligation is not assured to occur or be fulfilled.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5aa828819098ef55a70a0decbc |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.