Triple
T33028977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Renaming |
E845112
|
entity |
| Predicate | affectedStakeholder |
P29288
|
FINISHED |
| Object | Usenet administrators |
—
|
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: Usenet administrators | Statement: [Great Renaming, affectedStakeholder, Usenet administrators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedStakeholder Context triple: [Great Renaming, affectedStakeholder, Usenet administrators]
-
A.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
B.
affectedSubject
Indicates that an entity is the one that experiences or is impacted by an action, event, or condition.
-
C.
affectedCompany
Indicates that a company is impacted or influenced by a particular event, action, or entity.
-
D.
affectedPeople
Indicates the people who are impacted or influenced by a particular event, action, or condition.
-
E.
affectedEntity
chosen
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:24 a.m.