Triple
T38559389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMC Stubs A-List |
E928036
|
entity |
| Predicate | usageLimitType |
P98726
|
FINISHED |
| Object | number of movies per week |
—
|
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: number of movies per week | Statement: [AMC Stubs A-List, usageLimitType, number of movies per week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageLimitType Context triple: [AMC Stubs A-List, usageLimitType, number of movies per week]
-
A.
volumeLimitationBasis
Indicates the rule, criterion, or reference measure used as the basis for determining a limitation on volume.
-
B.
hasIntegrationLimitType
Indicates the type or nature of the integration limit applied in a given relationship or process.
-
C.
rateConstraint
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
D.
maximumUsage
chosen
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
E.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.