Triple
T6420750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metacritic |
E127936
|
entity |
| Predicate | aggregates |
P68691
|
FINISHED |
| Object | critics' reviews |
—
|
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: critics' reviews | Statement: [Metacritic, aggregates, critics' reviews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregates Context triple: [Metacritic, aggregates, critics' reviews]
-
A.
aggregationProperty
chosen
Indicates that one entity serves as an aggregation or summary of values or instances associated with another entity.
-
B.
aggregateState
Indicates the overall or combined condition or status resulting from multiple underlying states or components.
-
C.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
D.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
E.
summarizes
Indicates that one entity provides a concise representation or overview of the main points or content of another entity.
- 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.