Triple
T23284230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven-Card Stud |
E588944
|
entity |
| Predicate | informationStructure |
P151689
|
FINISHED |
| Object | combination of private and public cards |
—
|
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: combination of private and public cards | Statement: [Seven-Card Stud, informationStructure, combination of private and public cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationStructure Context triple: [Seven-Card Stud, informationStructure, combination of private and public cards]
-
A.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
internalStructure
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
D.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
E.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
- F. None of above. chosen
Provenance (4 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196454b4c8190a797537ce8912241 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:58 p.m.