Triple
T1745814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meta-Wiki |
E38332
|
entity |
| Predicate | accessibleAtURL |
P6055
|
FINISHED |
| Object | https://meta.wikimedia.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://meta.wikimedia.org | Statement: [Meta-Wiki, accessibleAtURL, https://meta.wikimedia.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleAtURL Context triple: [Meta-Wiki, accessibleAtURL, https://meta.wikimedia.org]
-
A.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
C.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
D.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
E.
textAvailableAt
Indicates that a specific piece of text can be accessed or obtained at a given location, source, or resource.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab630e7d008190a8c673665d9672bb |
completed | March 6, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69aa61c5a18481909bc49e0c54d64314 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.