Triple
T7944555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoDaddy |
E184466
|
entity |
| Predicate | hasCustomerBaseIn |
P77700
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [GoDaddy, hasCustomerBaseIn, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerBaseIn Context triple: [GoDaddy, hasCustomerBaseIn, worldwide]
-
A.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
C.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
-
D.
hasBaseRegion
Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
-
E.
hasNotableConsumerBase
chosen
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0e84448190a7e8e0749776a592 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.