Triple
T23894373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Line |
E600862
|
entity |
| Predicate | starsBandMember |
P45823
|
FINISHED |
| Object | Lance Bass |
—
|
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: Lance Bass | Statement: [On the Line, starsBandMember, Lance Bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsBandMember Context triple: [On the Line, starsBandMember, Lance Bass]
-
A.
houseBandMember
Indicates that a person is a member of a house band, typically performing regularly as part of that resident musical group.
-
B.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
C.
featuresBandMembers
chosen
Indicates that something includes or presents specific band members as part of its content or composition.
-
D.
notableBandMember
Indicates that the subject is a member of the band in the object and is recognized as particularly prominent or significant within that band.
-
E.
featuresFormerBandMemberOf
Indicates that the subject entity includes, highlights, or presents an individual who was previously a member of the referenced band.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdd857d081908740c4abb246c2ba |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.