Triple
T28833345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Arcadia |
E728108
|
entity |
| Predicate | idealizedIn |
P51621
|
FINISHED |
| Object | Roman literature |
—
|
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: Roman literature | Statement: [Ancient Arcadia, idealizedIn, Roman literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idealizedIn Context triple: [Ancient Arcadia, idealizedIn, Roman literature]
-
A.
hasIdealization
chosen
Indicates that one entity is a simplified, abstracted, or ideal form or model of another entity, capturing its essential features while omitting complexities.
-
B.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
C.
hasIdeal
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
D.
isIdealisticComparedTo
Indicates that one entity is characterized as more idealistic in attitude, beliefs, or approach when compared to another entity.
-
E.
idealQuality
Indicates that one entity possesses a quality or attribute that is considered ideal, optimal, or most desirable in relation to another entity or context.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:38 a.m.