Triple
T35866614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retta |
E1037106
|
entity |
| Predicate | socialMediaUsername |
P189484
|
FINISHED |
| Object | unfoRETTAble |
—
|
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: unfoRETTAble | Statement: [Retta, socialMediaUsername, unfoRETTAble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialMediaUsername Context triple: [Retta, socialMediaUsername, unfoRETTAble]
-
A.
twitterUsername
Indicates that one entity is the Twitter handle or username associated with another entity.
-
B.
instagramUsername
Indicates that one entity is the Instagram handle or username associated with another entity.
-
C.
githubUsername
Indicates that one entity is the GitHub account username associated with another entity.
-
D.
screenName
Indicates the display or handle name associated with an entity, typically used as its visible identifier in user interfaces or social platforms.
-
E.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
- F. None of above. chosen
Provenance (4 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:06 p.m.