Triple
T25456266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psammuthes |
E637921
|
entity |
| Predicate | nameTransmittedIn |
P77948
|
FINISHED |
| Object | Greek sources |
—
|
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: Greek sources | Statement: [Psammuthes, nameTransmittedIn, Greek sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameTransmittedIn Context triple: [Psammuthes, nameTransmittedIn, Greek sources]
-
A.
transcribedName
Indicates that one entity is a written or phonetic rendering of another entity’s name, typically adapted to a different script, language, or transcription system.
-
B.
nameProposedIn
Indicates that a particular name was suggested or put forward within a specific proposal, context, or event.
-
C.
nameWrittenIn
chosen
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
-
D.
namesAs
Indicates that one entity assigns or uses a particular name or label to refer to another entity.
-
E.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:09 p.m.