Triple
T4832122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki |
E107967
|
entity |
| Predicate | supportsImportExport |
P60286
|
FINISHED |
| Object | XML page import and export |
—
|
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: XML page import and export | Statement: [MediaWiki, supportsImportExport, XML page import and export]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsImportExport Context triple: [MediaWiki, supportsImportExport, XML page import and export]
-
A.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
C.
supportsElectronicCustomsDocuments
Indicates that one entity enables or accepts the use of electronic customs documentation in its interactions with another entity.
-
D.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
supportsInternationalization
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:24 p.m.