Triple
T1846716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colchis |
E41299
|
entity |
| Predicate | famedAs |
P22
|
FINISHED |
| Object | destination of Jason and the Argonauts |
—
|
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: destination of Jason and the Argonauts | Statement: [Colchis, famedAs, destination of Jason and the Argonauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famedAs Context triple: [Colchis, famedAs, destination of Jason and the Argonauts]
-
A.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
B.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
D.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
-
E.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.