Triple
T26408405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent cipher |
E663892
|
entity |
| Predicate | AESCompetitionStatus |
P83772
|
FINISHED |
| Object | finalist |
—
|
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: finalist | Statement: [Serpent cipher, AESCompetitionStatus, finalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESCompetitionStatus Context triple: [Serpent cipher, AESCompetitionStatus, finalist]
-
A.
competitionStatus
Indicates the current state or phase of a competition, such as whether it is upcoming, ongoing, paused, or completed.
-
B.
statusInCompetition
chosen
Indicates the current standing or role an entity holds within a specific competition or contest.
-
C.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
D.
challengerStatus
Indicates the role or condition of an entity as a challenger in a competitive or adversarial context.
-
E.
competitionEntries
Indicates that one entity has submitted or is associated with one or more entries in a competition involving 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_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_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:36 p.m.