Triple
T23787071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tayo |
E587981
|
entity |
| Predicate | hasCloseBondWith |
P68132
|
FINISHED |
| Object | Rocky |
—
|
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: Rocky | Statement: [Tayo, hasCloseBondWith, Rocky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloseBondWith Context triple: [Tayo, hasCloseBondWith, Rocky]
-
A.
bondedWith
chosen
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
C.
hasSocialTieWith
Indicates a social relationship or connection exists between two entities, such as friendship, acquaintance, or other interpersonal tie.
-
D.
hasStrongTiesTo
Indicates a close, influential, and enduring relationship or connection exists between the referenced entities.
-
E.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c6321c5c819084db8f9ef0946326 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:17 p.m.