Triple
T15062415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Hodak |
E379661
|
entity |
| Predicate | usesSocialMediaFor |
P20322
|
FINISHED |
| Object | discussing technology |
—
|
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: discussing technology | Statement: [Max Hodak, usesSocialMediaFor, discussing technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSocialMediaFor Context triple: [Max Hodak, usesSocialMediaFor, discussing technology]
-
A.
socialMedia
chosen
Indicates a relationship where one entity uses, is associated with, or interacts through social networking or content-sharing platforms with another entity.
-
B.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
C.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
D.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
-
E.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee6a55c8190b40c4672fb46b79b |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.