Triple
T34954913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTAN |
E1008099
|
entity |
| Predicate | fileAccessURL |
P6055
|
FINISHED |
| Object | https://ctan.org/tex-archive |
—
|
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://ctan.org/tex-archive | Statement: [CTAN, fileAccessURL, https://ctan.org/tex-archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileAccessURL Context triple: [CTAN, fileAccessURL, https://ctan.org/tex-archive]
-
A.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
accessPath
Indicates a path, route, or means by which something can be reached, entered, or accessed.
-
C.
hasAccessURL
Indicates that an entity is associated with a specific URL through which it can be accessed or retrieved.
-
D.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
-
E.
filePath
Indicates the relationship that specifies the location or directory path where a file is stored in a file system.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.