Triple
T28980044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tammy Larsen |
E734522
|
entity |
| Predicate | sometimesFriendsWith |
P150269
|
FINISHED |
| Object | Tina Belcher |
—
|
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: Tina Belcher | Statement: [Tammy Larsen, sometimesFriendsWith, Tina Belcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesFriendsWith Context triple: [Tammy Larsen, sometimesFriendsWith, Tina Belcher]
-
A.
acquaintanceOf
Indicates that one entity knows another in a casual or non-intimate way, without implying close friendship or strong personal ties.
-
B.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
-
C.
hasSocialTieWith
chosen
Indicates a social relationship or connection exists between two entities, such as friendship, acquaintance, or other interpersonal tie.
-
D.
friendAndTeammate
Indicates that one entity has a relationship with another in which they are both friends and members of the same team.
-
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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee362b081909decc8d1aa60ecab |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:10 a.m.