Triple
T17524073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyler Hubbard |
E426749
|
entity |
| Predicate | notableSoloSingle |
P33935
|
FINISHED |
| Object | 5 Foot 9 |
—
|
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: 5 Foot 9 | Statement: [Tyler Hubbard, notableSoloSingle, 5 Foot 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSoloSingle Context triple: [Tyler Hubbard, notableSoloSingle, 5 Foot 9]
-
A.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
B.
notableSingleChartPerformance
chosen
Indicates that an entity achieved a particularly significant or distinguished performance on a music singles chart.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
E.
hasSoloAlbum
Indicates that an individual has released at least one music album as a solo artist, separate from any group or band projects.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d4db60819096a03dbc4254850f |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.