Triple
T16702659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firefox Relay |
E405889
|
entity |
| Predicate | paidTierIncludes |
P124299
|
FINISHED |
| Object | higher alias limits |
—
|
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: higher alias limits | Statement: [Firefox Relay, paidTierIncludes, higher alias limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paidTierIncludes Context triple: [Firefox Relay, paidTierIncludes, higher alias limits]
-
A.
paidTierName
Indicates the specific name or label of the paid subscription tier associated with an entity.
-
B.
premiumTierBackedBy
Indicates that a premium tier is supported, guaranteed, or underwritten by a specified backing entity or resource.
-
C.
promotionIncludes
Indicates that a particular promotion encompasses, covers, or applies to a specified item, service, or condition.
-
D.
isPremiumTierAvailable
Indicates whether access to a premium-level tier or service option is currently available.
-
E.
membershipIncluded
Indicates that one entity’s membership or inclusion is contained within, or granted as part of, another entity’s membership.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38333a6908190a17d2dee2ca622d6 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:19 a.m.