Triple
T19423598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floyd Henderson |
E485921
|
entity |
| Predicate | relationshipToLouisHinds |
P135824
|
FINISHED |
| Object | former singing partner |
—
|
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: former singing partner | Statement: [Floyd Henderson, relationshipToLouisHinds, former singing partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLouisHinds Context triple: [Floyd Henderson, relationshipToLouisHinds, former singing partner]
-
A.
relationshipWithLouisWinthorpeIII
Indicates the existence or nature of a relationship between an entity and Louis Winthorpe III.
-
B.
relationshipToHenry
Indicates the specific type of relationship or connection that an entity has to Henry.
-
C.
relationshipToLloyd
Indicates the specific type of personal or social relationship an entity has with Lloyd.
-
D.
relationshipToTinaBordereau
Indicates the specific type of personal or professional relationship an entity has with Tina Bordereau.
-
E.
Lincoln Lewis
Indicates a relationship or association involving the entity or name "Lincoln Lewis," such as authorship, participation, or attribution in a given context.
- F. None of above. chosen
Provenance (4 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e632169d9c81909a88704c6beb8fe0 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.