Triple
T28630120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian Wikiquote |
E724618
|
entity |
| Predicate | hasSourcedQuotations |
P141050
|
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: [Hungarian Wikiquote, hasSourcedQuotations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourcedQuotations Context triple: [Hungarian Wikiquote, hasSourcedQuotations, true]
-
A.
quotedOn
Indicates that one entity is cited, referenced, or mentioned within another source, document, or context.
-
B.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
C.
hasQuotationStatus
Indicates that an entity has a particular quotation-related state or condition (such as being quoted, unquoted, or having a specific quotation status).
-
D.
hasQuotationSystem
Indicates that an entity uses or is associated with a particular system or convention for representing quotations.
-
E.
hasSourceOfData
chosen
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 4:37 a.m.