Triple
T3776370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father Stretch My Hands, Pt. 1 |
E83316
|
entity |
| Predicate | hasIntroTag |
P42616
|
FINISHED |
| Object | If young Metro don’t trust you, I’m gon’ shoot you |
—
|
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: If young Metro don’t trust you, I’m gon’ shoot you | Statement: [Father Stretch My Hands, Pt. 1, hasIntroTag, If young Metro don’t trust you, I’m gon’ shoot you]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntroTag Context triple: [Father Stretch My Hands, Pt. 1, hasIntroTag, If young Metro don’t trust you, I’m gon’ shoot you]
-
A.
hasIntroduction
chosen
Indicates that one entity includes or provides an introductory section, part, or presentation for another entity.
-
B.
hasHeading
Indicates that one entity serves as a heading or title for another entity.
-
C.
hasParagraph
Indicates that one entity contains or is associated with a specific paragraph as part of its content or structure.
-
D.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc5be3c48190a72e840d8214bb74 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.