Triple
T8247894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AUR |
E192891
|
entity |
| Predicate | webInterfaceURL |
P6055
|
FINISHED |
| Object | https://aur.archlinux.org |
—
|
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: https://aur.archlinux.org | Statement: [AUR, webInterfaceURL, https://aur.archlinux.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: webInterfaceURL Context triple: [AUR, webInterfaceURL, https://aur.archlinux.org]
-
A.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
B.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
C.
webPage
Indicates that one entity is a web page associated with, describing, or providing information about another entity.
-
D.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
E.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7875318c819095f971ba513c54fd |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.