Triple
T28628997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Wikisource |
E724592
|
entity |
| Predicate | hasInterwikiPrefix |
P82626
|
FINISHED |
| Object | zhwikisource |
—
|
NE NERFINISHED |
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: zhwikisource | Statement: [Chinese Wikisource, hasInterwikiPrefix, zhwikisource]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterwikiPrefix Context triple: [Chinese Wikisource, hasInterwikiPrefix, zhwikisource]
-
A.
usesInterwikiLinks
chosen
Indicates that one entity includes or relies on interwiki links to reference or connect to content in other wikis.
-
B.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
C.
hasAbbreviationPrefix
Indicates that one term’s abbreviation begins with the same initial sequence of characters as another specified string or term.
-
D.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
-
E.
hasWikidataProperty
Indicates that one entity is associated with a specific Wikidata property used to describe or qualify it.
- 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_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 28, 2026, 4:37 a.m.