Triple
T5007680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchises |
E112535
|
entity |
| Predicate | roleInAeneid |
P9987
|
FINISHED |
| Object | reveals future Roman heroes to Aeneas |
—
|
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: reveals future Roman heroes to Aeneas | Statement: [Anchises, roleInAeneid, reveals future Roman heroes to Aeneas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAeneid Context triple: [Anchises, roleInAeneid, reveals future Roman heroes to Aeneas]
-
A.
goalOfAeneas
Indicates that the specified entity represents a goal, aim, or objective pursued by Aeneas.
-
B.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
C.
VirgilRepresents
Indicates that Virgil serves as a symbolic or representative figure for someone or something, embodying their role, qualities, or perspective.
-
D.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.