Triple
T4736916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaeacians |
E105146
|
entity |
| Predicate | perceivedByGreeksAs |
P46173
|
FINISHED |
| Object | idealized civilized hosts |
—
|
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: idealized civilized hosts | Statement: [Phaeacians, perceivedByGreeksAs, idealized civilized hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedByGreeksAs Context triple: [Phaeacians, perceivedByGreeksAs, idealized civilized hosts]
-
A.
typeOfGreek
Indicates that one entity is a specific kind or category of Greek associated with the other entity.
-
B.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
-
C.
GreekForcesIncluded
Indicates that a set of forces or troops includes Greek military units as part of its composition.
-
D.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
E.
reputationInAntiquity
chosen
Indicates the reputation or standing an entity had during ancient times.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.