Triple
T21141292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lukomorye oak tree |
E520933
|
entity |
| Predicate | timeOfFirstLiteraryAttestation |
P3921
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Lukomorye oak tree, timeOfFirstLiteraryAttestation, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFirstLiteraryAttestation Context triple: [Lukomorye oak tree, timeOfFirstLiteraryAttestation, early 19th century]
-
A.
firstWellKnownLiteraryVersionYear
Indicates the year in which the first well-known literary version of something (such as a story, character, or motif) was published or recorded.
-
B.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
C.
firstPoemWrittenAt
Indicates the time or date at which an entity’s first poem was written.
-
D.
timeOfMajorLiteraryFormulation
Indicates the time period during which a major or definitive literary formulation of something was created or established.
-
E.
firstLatinTranslationDate
Indicates the date on which something was first translated into Latin.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723f96cf081909d10309e08aeca93 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.