Triple
T34749055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lechia |
E1001717
|
entity |
| Predicate | usedPoeticallyFor |
P181571
|
FINISHED |
| Object | the Polish state |
—
|
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: the Polish state | Statement: [Lechia, usedPoeticallyFor, the Polish state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPoeticallyFor Context triple: [Lechia, usedPoeticallyFor, the Polish state]
-
A.
usedByPoet
Indicates that something (such as a word, style, device, or object) is employed or utilized by a poet.
-
B.
poeticParaphrasedIn
Indicates that one expression is rendered as a poetic or stylistically embellished paraphrase of another expression.
-
C.
usesPoeticProgram
Indicates that one entity employs or applies a poetic program—such as a structured, rule-based, or stylistically poetic system—in relation to another entity or context.
-
D.
literaryUse
Indicates that something is employed or referenced within a literary context, such as in a written work, style, or technique.
-
E.
exemplifiedByPoet
Indicates that something is characteristically or ideally represented by a particular poet.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.