Triple
T24684546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelp |
E611244
|
entity |
| Predicate | hasUserAccountType |
P5098
|
FINISHED |
| Object | business owner accounts |
—
|
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: business owner accounts | Statement: [Yelp, hasUserAccountType, business owner accounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserAccountType Context triple: [Yelp, hasUserAccountType, business owner accounts]
-
A.
accountType
Indicates the specific category or classification of an account within a system or context.
-
B.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
C.
hasAdministrativeType
Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
-
D.
supportsAccountType
chosen
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
E.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:17 a.m.