Triple
T27227298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἄκαμας |
E682050
|
entity |
| Predicate | servedOnSide |
P188869
|
FINISHED |
| Object | Greeks |
—
|
NE NERFINISHED |
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: Greeks | Statement: [Ἄκαμας, servedOnSide, Greeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedOnSide Context triple: [Ἄκαμας, servedOnSide, Greeks]
-
A.
servedForSide
Indicates that something is provided or presented as an accompaniment or side item to a main dish or primary element.
-
B.
servesSide
Indicates that one entity is provided or presented as an accompanying side item to another primary entity.
-
C.
servesBoroughOrSide
Indicates that something (such as a service, route, or facility) provides service to or covers a particular borough or side of a geographic area.
-
D.
servedTogetherWith
Indicates that two entities were provided, offered, or used at the same time as part of the same service, event, or context.
-
E.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
- F. None of above. chosen
Provenance (4 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 27, 2026, 9:45 a.m.