Triple
T26523409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punky Brewster |
E670620
|
entity |
| Predicate | networkForRevival |
P44891
|
FINISHED |
| Object | Peacock |
—
|
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: Peacock | Statement: [Punky Brewster, networkForRevival, Peacock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkForRevival Context triple: [Punky Brewster, networkForRevival, Peacock]
-
A.
revivalPlatform
chosen
Indicates that an entity serves as the medium, venue, or system through which another entity is brought back, renewed, or reintroduced after a period of decline or inactivity.
-
B.
revival2011Network
Indicates a network or system that was reactivated, relaunched, or brought back into operation in 2011.
-
C.
revivalCenter
Indicates that an entity serves as a central place or hub where revival, restoration, or renewal activities for another entity occur.
-
D.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or exchange.
-
E.
formerNetwork
Indicates that an entity was previously part of, or affiliated with, a particular network but is no longer currently associated with it.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:29 a.m.