Triple
T28627804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Wikipedia |
E724567
|
entity |
| Predicate | supportsWikidataIntegration |
P164957
|
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: [Italian Wikipedia, supportsWikidataIntegration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWikidataIntegration Context triple: [Italian Wikipedia, supportsWikidataIntegration, true]
-
A.
usesWikidata
chosen
Indicates that one entity makes use of or relies on Wikidata as a data source or reference.
-
B.
hasWikidataItem
Indicates that an entity is associated with a specific corresponding item in the Wikidata knowledge base.
-
C.
hasWikidataProperty
Indicates that one entity is associated with a specific Wikidata property used to describe or qualify it.
-
D.
mayBeIntegratedWith
Indicates that one entity has the potential or capability to be combined or incorporated with another entity into a unified or interoperable whole.
-
E.
microdataAvailability
Indicates that detailed, record-level data (microdata) associated with an entity is available for access or use.
- 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_6a01926e2f348190a632eff5c91db5e0 |
completed | May 11, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a01923488f4819094d79a27f4bc8ab8 |
completed | May 11, 2026, 8:24 a.m. |
Created at: April 28, 2026, 4:36 a.m.