Triple
T14478027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leontine embassy to Athens |
E359024
|
entity |
| Predicate | hasEnvoyRole |
P161
|
FINISHED |
| Object | Gorgias as spokesman |
—
|
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: Gorgias as spokesman | Statement: [Leontine embassy to Athens, hasEnvoyRole, Gorgias as spokesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvoyRole Context triple: [Leontine embassy to Athens, hasEnvoyRole, Gorgias as spokesman]
-
A.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
C.
hasEnsembleRoleWith
Indicates that two or more entities share a collaborative or joint role within the same ensemble, group, or collective context.
-
D.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
E.
hasFranchiseRole
Indicates that an entity holds a specific role or position within a franchise relationship.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.