Triple
T12206573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Charset |
E290850
|
entity |
| Predicate | exampleClient |
P8616
|
FINISHED |
| Object | web browser |
—
|
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 browser | Statement: [Accept-Charset, exampleClient, web browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleClient Context triple: [Accept-Charset, exampleClient, web browser]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
C.
clientFor
chosen
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
D.
exampleType
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another entity.
-
E.
exampleClass
Indicates that the subject belongs to, is categorized under, or serves as an instance of a particular class or type.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.