Triple
T11338731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quentin Jacobsen |
E268539
|
entity |
| Predicate | closeFriendGroup |
P30021
|
FINISHED |
| Object | Ben Starling and Radar |
—
|
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: Ben Starling and Radar | Statement: [Quentin Jacobsen, closeFriendGroup, Ben Starling and Radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeFriendGroup Context triple: [Quentin Jacobsen, closeFriendGroup, Ben Starling and Radar]
-
A.
closeRelationship
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
-
B.
friendGroupRole
Indicates the specific role or function an individual holds within a particular friend group.
-
C.
socialCircle
chosen
Indicates that one entity belongs to, or is part of, the group of people with whom another entity regularly interacts socially.
-
D.
closeAlly
Indicates a strong, trusted alliance or partnership between two entities, characterized by mutual support and cooperation.
-
E.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea008b5081908e6c6c6fc29ef936 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.