Triple
T36211848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-Town |
E1047573
|
entity |
| Predicate | notableSongwriterMember |
P204792
|
FINISHED |
| Object | Jacob Underwood |
E431378
|
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: Jacob Underwood | Statement: [O-Town, notableSongwriterMember, Jacob Underwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSongwriterMember Context triple: [O-Town, notableSongwriterMember, Jacob Underwood]
-
A.
notableSongwriterOn
Indicates that one entity is recognized as a notable songwriter contributing to or associated with another entity (such as a musical work or recording).
-
B.
notableLyricist
Indicates that the subject is a lyricist who is particularly distinguished or well-known for their work.
-
C.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
D.
hasPrimarySongwriters
Indicates that one or more entities are the main creators responsible for writing a particular song.
-
E.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
- F. None of above. chosen
Provenance (5 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a394d2e554881909d1c249a51781aaa |
completed | June 22, 2026, 2:56 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.