Triple
T35193317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Chenowith |
E1016180
|
entity |
| Predicate | hasOnAndOffRelationshipWith |
P121897
|
FINISHED |
| Object | Claire Fisher |
—
|
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: Claire Fisher | Statement: [Billy Chenowith, hasOnAndOffRelationshipWith, Claire Fisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnAndOffRelationshipWith Context triple: [Billy Chenowith, hasOnAndOffRelationshipWith, Claire Fisher]
-
A.
hasOnAgainOffAgainRelationshipWith
chosen
Indicates a romantic relationship between two people that repeatedly alternates between being together and breaking up over time.
-
B.
hasContrastingRelationshipWith
Indicates a relationship in which two entities are opposed, divergent, or markedly different in qualities, roles, or effects.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
hasRelationshipToElectricLight
Indicates that one entity has a specified type of connection, association, or relevance to an electric light.
-
E.
isOff
Indicates that an entity is currently inactive, powered down, or not in operation.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:02 p.m.