Triple
T14646663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psyche |
E343867
|
entity |
| Predicate | romanNameContext |
P6662
|
FINISHED |
| Object | Psyche in Latin 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: Psyche in Latin literature | Statement: [Psyche, romanNameContext, Psyche in Latin literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanNameContext Context triple: [Psyche, romanNameContext, Psyche in Latin literature]
-
A.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
B.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
C.
hasRomanName
chosen
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
D.
preRomanContext
Indicates that something exists, occurs, or is situated in a historical or cultural context prior to the Roman period.
-
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ebe8048190a2935d00c9cfd8be |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.