Triple
T8486623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Language |
E200846
|
entity |
| Predicate | clientSets |
P83551
|
FINISHED |
| Object | web browsers |
—
|
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: web browsers | Statement: [Accept-Language, clientSets, web browsers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientSets Context triple: [Accept-Language, clientSets, web browsers]
-
A.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
managedClient
Indicates that one entity serves as a client that is overseen, administered, or handled operationally by another entity.
-
D.
intendedClients
Indicates the entities that a product, service, or action is specifically designed or targeted to serve as clients.
-
E.
clientSDKPlatform
Indicates the software platform or environment on which a client-side SDK is designed to run or be used.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.