Triple
T33371127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Cups |
E854492
|
entity |
| Predicate | positionInSuit |
P108710
|
FINISHED |
| Object | highest court card of Cups |
—
|
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: highest court card of Cups | Statement: [King of Cups, positionInSuit, highest court card of Cups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSuit Context triple: [King of Cups, positionInSuit, highest court card of Cups]
-
A.
positionInCard
Indicates the relative placement or ordering of an element within a specific card.
-
B.
cardPosition
chosen
Indicates the specific place or order a card occupies within a sequence, deck, or layout.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionInDuo
Indicates the specific role or placement an entity holds within a two-member grouping or partnership.
-
E.
cardBackPosition
Indicates the spatial location or orientation of the back side of a card relative to a reference frame or other objects.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 1:35 a.m.