Triple
T16317589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcy Rhoades |
E396210
|
entity |
| Predicate | relationshipToBundys |
P116865
|
FINISHED |
| Object | next-door neighbor |
—
|
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: next-door neighbor | Statement: [Marcy Rhoades, relationshipToBundys, next-door neighbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToBundys Context triple: [Marcy Rhoades, relationshipToBundys, next-door neighbor]
-
A.
relationshipToAlBundy
chosen
Indicates the specific familial, social, or personal relationship that an entity has to the person Al Bundy.
-
B.
relationshipToJewelBundren
Indicates the specific familial or interpersonal connection that one entity has to Jewel Bundren.
-
C.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b31b988190bb1fde36dae11bbd |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.