Triple
T21884027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyidus |
E540359
|
entity |
| Predicate | usedSign |
P9766
|
FINISHED |
| Object | color of a cow among Minos’s herds |
—
|
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: color of a cow among Minos’s herds | Statement: [Polyidus, usedSign, color of a cow among Minos’s herds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSign Context triple: [Polyidus, usedSign, color of a cow among Minos’s herds]
-
A.
usedPass
Indicates that one entity has utilized or redeemed a pass, ticket, or similar authorization instrument.
-
B.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
C.
usedCross
Indicates that one entity made use of a cross-shaped object or structure, or traversed by means of a crossing point such as a crosswalk or intersection.
-
D.
hasSign
chosen
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
E.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e9d3508190aadcfcdac0376387 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.