Triple
T11390960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMC Classic |
E269832
|
entity |
| Predicate | hasCustomerExperienceLevel |
P5308
|
FINISHED |
| Object | no-frills |
—
|
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: no-frills | Statement: [AMC Classic, hasCustomerExperienceLevel, no-frills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerExperienceLevel Context triple: [AMC Classic, hasCustomerExperienceLevel, no-frills]
-
A.
typicalExperienceLevel
Indicates the usual or most common level of experience associated with an entity in a given context.
-
B.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
C.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
D.
hasGlobalExperience
Indicates that an entity possesses experience gained from working, operating, or engaging across multiple countries or international contexts.
-
E.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.