Triple
T20502127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenaeum fragments |
E503329
|
entity |
| Predicate | conceptElaborated |
P134763
|
FINISHED |
| Object | romantic irony |
—
|
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: romantic irony | Statement: [Athenaeum fragments, conceptElaborated, romantic irony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptElaborated Context triple: [Athenaeum fragments, conceptElaborated, romantic irony]
-
A.
refinedConcept
Indicates that one concept is a more precise, detailed, or specialized version of another concept.
-
B.
expandsConcept
chosen
Indicates that one concept broadens, elaborates, or adds detail to the meaning or scope of another concept.
-
C.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
D.
conceptualAspect
Indicates that one entity represents an abstract, conceptual, or non-physical aspect, feature, or dimension of another entity.
-
E.
conceptualizedFor
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc272a481909329ecd1560989ef |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.