Triple
T6420782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metacritic |
E127936
|
entity |
| Predicate | collectsDataFrom |
P2191
|
FINISHED |
| Object | professional publications |
—
|
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: professional publications | Statement: [Metacritic, collectsDataFrom, professional publications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsDataFrom Context triple: [Metacritic, collectsDataFrom, professional publications]
-
A.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
B.
collectsFrom
chosen
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
C.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
D.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
E.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06902ddb48190bd5a8b5ecdf6c39e |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.