Triple
T34728483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann (The Queen of Spades) |
E1001136
|
entity |
| Predicate | thirdCard |
P62307
|
FINISHED |
| Object | queen of spades |
—
|
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: queen of spades | Statement: [Hermann (The Queen of Spades), thirdCard, queen of spades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdCard Context triple: [Hermann (The Queen of Spades), thirdCard, queen of spades]
-
A.
thirdElement
chosen
Indicates that one entity is the third element in an ordered sequence or tuple associated with another entity.
-
B.
thirdWord
Indicates that one entity is the third word in sequence within another entity (such as a text or phrase).
-
C.
thirdSingle
Indicates that an entity is the third single (e.g., third single release) associated with another entity, typically in a sequence such as from an album or artist.
-
D.
thirdFactor
Indicates that an entity serves as the third factor or element in a multi-factor relationship, typically complementing two other primary factors in a given context.
-
E.
thirdRankSee
Indicates that an entity occupying a third rank or position observes, notices, or visually perceives 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 3:59 p.m.