Triple
T12544000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Professional Web |
E299913
|
entity |
| Predicate | promotesUseOf |
P34894
|
FINISHED |
| Object | .pw for corporate sites |
—
|
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: .pw for corporate sites | Statement: [The Professional Web, promotesUseOf, .pw for corporate sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesUseOf Context triple: [The Professional Web, promotesUseOf, .pw for corporate sites]
-
A.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
B.
recommendsUseOf
chosen
Indicates that one entity advises, endorses, or suggests the use of another entity as appropriate or beneficial in a given context.
-
C.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
D.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.