Triple
T27157559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gizmodo |
E682562
|
entity |
| Predicate | hasSisterWebsite |
P16554
|
FINISHED |
| Object | Jezebel |
—
|
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: Jezebel | Statement: [Gizmodo, hasSisterWebsite, Jezebel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterWebsite Context triple: [Gizmodo, hasSisterWebsite, Jezebel]
-
A.
hasSisterSite
chosen
Indicates that one site is formally associated with another as a sister site, typically implying a parallel or closely related counterpart.
-
B.
hasSister
Indicates that one entity is the sister of another entity.
-
C.
hasSisterOrganization
Indicates that one organization is related to another as a sister organization, typically sharing a common parent, affiliation, or parallel status within the same overarching structure.
-
D.
hasCompanionWebsite
Indicates that something is associated with or supported by a dedicated companion website.
-
E.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 9:17 a.m.