Triple
T28043353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moxie |
E708607
|
entity |
| Predicate | hasConsumerBase |
P200121
|
FINISHED |
| Object | New England residents |
—
|
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: New England residents | Statement: [Moxie, hasConsumerBase, New England residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsumerBase Context triple: [Moxie, hasConsumerBase, New England residents]
-
A.
hasNotableConsumerBase
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
-
B.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
C.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
E.
hasCustomerBaseType
Indicates that an entity is associated with a particular fundamental category or type of customers it serves or targets.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
| PDg | Predicate description generation | batch_69ff76ab9b4c8190b4cc7c9c733b2765 |
completed | May 9, 2026, 6:02 p.m. |
Created at: April 27, 2026, 8:27 p.m.