Triple
T28592968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Wikisource |
E723703
|
entity |
| Predicate | usesProofreadPageExtension |
P174276
|
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: [Ukrainian Wikisource, usesProofreadPageExtension, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProofreadPageExtension Context triple: [Ukrainian Wikisource, usesProofreadPageExtension, true]
-
A.
usesProofLanguage
Indicates that one entity employs a specific formal or structured language to express or present a proof related to another entity.
-
B.
hasProofMark
Indicates that an entity bears a specific proof mark signifying it has passed an official test or inspection.
-
C.
originalProof
Indicates that one entity serves as the initial or primary proof or evidence supporting another entity.
-
D.
requiresProofIn
Indicates that one entity must be justified, validated, or supported by formal proof within the context or framework specified by another entity.
-
E.
includesCorrectionsFor
Indicates that one item contains modifications, fixes, or amendments that address errors or issues present in another item.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 28, 2026, 4:21 a.m.