Triple
T31710928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Turk |
E809313
|
entity |
| Predicate | hasFriendshipDynamic |
P26472
|
FINISHED |
| Object | bromance with J.D. |
—
|
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: bromance with J.D. | Statement: [Christopher Turk, hasFriendshipDynamic, bromance with J.D.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFriendshipDynamic Context triple: [Christopher Turk, hasFriendshipDynamic, bromance with J.D.]
-
A.
hasFriendship
chosen
Indicates a mutual, positive social relationship of friendship existing between two entities.
-
B.
bestFriendDynamicWith
Indicates a close, primary friendship relationship between two entities, typically characterized by mutual trust, support, and frequent positive interaction.
-
C.
baseFriendship
Indicates a basic or foundational friendship relationship that exists between two entities.
-
D.
hasFriends
Indicates that an entity is socially connected to one or more other entities in a friendship relationship.
-
E.
viewOnFriendship
Indicates a person's perspective, attitude, or beliefs about the nature and value of friendship.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 30, 2026, 11:15 p.m.