Triple
T3138804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West family |
E65593
|
entity |
| Predicate | socialMediaFollowing |
P21428
|
FINISHED |
| Object | large |
—
|
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: large | Statement: [West family, socialMediaFollowing, large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialMediaFollowing Context triple: [West family, socialMediaFollowing, large]
-
A.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
B.
followerOf
chosen
Indicates that one entity subscribes to, tracks, or regularly receives updates from another entity, typically in a social or informational context.
-
C.
layFollowers
Indicates that one entity is a non-ordained (lay) follower or adherent of another entity, typically a religious figure, institution, or tradition.
-
D.
socialMedia
Indicates a relationship where one entity uses, is associated with, or interacts through social networking or content-sharing platforms with another entity.
-
E.
eraFollowed
Indicates that one historical era comes directly after another in chronological sequence.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada575bbac81909b1b95126f488809 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.