Triple
T28592962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikisource |
E723703
|
entity |
| Predicate | namespaceCode |
P108285
|
FINISHED |
| Object | s |
—
|
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: s | Statement: [Ukrainian Wikisource, namespaceCode, s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namespaceCode Context triple: [Ukrainian Wikisource, namespaceCode, s]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
C.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
D.
internalCode
chosen
Indicates that an entity is associated with an internal identification code used within a specific system or organization.
-
E.
productionCode
Indicates the unique identifier or code assigned to a specific production (such as a film, TV episode, or manufactured item) that links related records or versions of that production.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:21 a.m.