Triple
T28629136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Wikipedia |
E724595
|
entity |
| Predicate | supportsInfoboxes |
P165761
|
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, supportsInfoboxes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInfoboxes Context triple: [Dutch Wikipedia, supportsInfoboxes, true]
-
A.
usesInfoboxes
chosen
Indicates that one entity employs or incorporates infoboxes in relation to another entity or within a given context.
-
B.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
E.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving another entity.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a019b8995dc819088727aa023beadce |
completed | May 11, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_6a01961bb748819096a941f1b5443908 |
completed | May 11, 2026, 8:40 a.m. |
Created at: April 28, 2026, 4:37 a.m.