Triple
T21933221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At the Movies |
E541622
|
entity |
| Predicate | hasCriticPairFormat |
P146606
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [At the Movies, hasCriticPairFormat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriticPairFormat Context triple: [At the Movies, hasCriticPairFormat, yes]
-
A.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
-
B.
hasCanonicalFormulation
Indicates that one entity is the standard or officially accepted formulation or expression of another entity.
-
C.
isPairOf
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
D.
hasCriticalDescriptor
Indicates that an entity is associated with a descriptor that marks it as critical, essential, or of high importance or severity.
-
E.
hasMatchFormat
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
- F. None of above. chosen
Provenance (4 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12400a1248190b3f8f27f2aa4a858 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:47 p.m.