Triple
T36574605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Computer Company |
E902209
|
entity |
| Predicate | publishedContentType |
P44878
|
FINISHED |
| Object | tutorials |
—
|
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: tutorials | Statement: [People’s Computer Company, publishedContentType, tutorials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedContentType Context triple: [People’s Computer Company, publishedContentType, tutorials]
-
A.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
B.
publishedTo
Indicates that something has been made publicly available or distributed to an audience, platform, or destination.
-
C.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
D.
documentTypePublished
chosen
Indicates that a specific type or category of document has been formally published or made publicly available.
-
E.
publishesContent
Indicates that one entity makes content created by another entity publicly available or distributed through some medium.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 3, 2026, 4:11 p.m.