Triple
T28629138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Wikipedia |
E724595
|
entity |
| Predicate | supportsRedirects |
P203526
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dutch Wikipedia, supportsRedirects, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRedirects Context triple: [Dutch Wikipedia, supportsRedirects, true]
-
A.
supportsCrossSiteRequests
Indicates that an entity allows or is compatible with making requests across different domains or origins.
-
B.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
C.
supportsLinks
Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
-
D.
supportsTransitions
Indicates that one entity enables, allows, or is compatible with changes from one state or condition to another.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- F. None of above. chosen
Provenance (4 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: April 28, 2026, 4:37 a.m.