Triple
T26408406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent cipher |
E663892
|
entity |
| Predicate | AESCompetitionRank |
P103031
|
FINISHED |
| Object | second place |
—
|
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: second place | Statement: [Serpent cipher, AESCompetitionRank, second place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESCompetitionRank Context triple: [Serpent cipher, AESCompetitionRank, second place]
-
A.
rankingPositions
chosen
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
B.
hasRankingStrength
Indicates the relative strength or priority of an entity’s ranking compared to others in a given ordering or evaluation.
-
C.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
D.
inspiredRanks
Indicates that one entity’s example, achievement, or influence motivates another entity to improve or elevate its status, performance, or position.
-
E.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:36 p.m.