Triple
T33319939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United mobile app |
E853109
|
entity |
| Predicate | requiresAccountForFullFunctionality |
P12367
|
FINISHED |
| Object | United MileagePlus account |
—
|
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: United MileagePlus account | Statement: [United mobile app, requiresAccountForFullFunctionality, United MileagePlus account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAccountForFullFunctionality Context triple: [United mobile app, requiresAccountForFullFunctionality, United MileagePlus account]
-
A.
requiresAccountForEmail
Indicates that performing the email-related action is only possible if the user has an associated account.
-
B.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
-
C.
administrationRequired
Indicates that a particular action, process, or resource can only be performed, accessed, or modified when administrative authorization or privileges are present.
-
D.
membershipRequired
chosen
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
E.
requiresAccountToWatch
Indicates that accessing or viewing the content is only possible if the user has an account.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 1:33 a.m.