Triple
T18531122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Debug Toolbar |
E452831
|
entity |
| Predicate | linkTo |
P68422
|
FINISHED |
| Object | detailed profiler pages |
—
|
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: detailed profiler pages | Statement: [Web Debug Toolbar, linkTo, detailed profiler pages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkTo Context triple: [Web Debug Toolbar, linkTo, detailed profiler pages]
-
A.
navigationLinkedTo
chosen
Indicates that one element is connected to another as a navigational target or destination, enabling movement or access between them.
-
B.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
C.
linkedSite
Indicates that one site has an explicit hyperlink or reference connection to another site.
-
D.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
E.
formsLinkIn
Indicates that one entity creates or establishes a connection or linkage within another entity or structure.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fd0e348190ab3d4548f74b9b79 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.