Triple
T19703534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic MediaWiki |
E473153
|
entity |
| Predicate | turnsContentInto |
P631
|
FINISHED |
| Object | structured knowledge base |
—
|
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: structured knowledge base | Statement: [Semantic MediaWiki, turnsContentInto, structured knowledge base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnsContentInto Context triple: [Semantic MediaWiki, turnsContentInto, structured knowledge base]
-
A.
createsContentFor
Indicates that one entity produces or generates content intended to be used by or directed toward another entity.
-
B.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
C.
publishesContent
Indicates that one entity makes content created by another entity publicly available or distributed through some medium.
-
D.
turnsIn
Indicates that an entity submits or hands over something, typically work or an item, to another party or authority.
-
E.
convertsTo
chosen
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b8707081908fbf96c989d2d52d |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.