Triple
T31229550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gambler Returns: The Luck of the Draw |
E796240
|
entity |
| Predicate | featuresCrossoverFrom |
P8704
|
FINISHED |
| Object | Maverick |
—
|
NE NERFINISHED |
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: Maverick | Statement: [The Gambler Returns: The Luck of the Draw, featuresCrossoverFrom, Maverick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCrossoverFrom Context triple: [The Gambler Returns: The Luck of the Draw, featuresCrossoverFrom, Maverick]
-
A.
featuresCrossoverWith
chosen
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
B.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
C.
featuresCrossoverStyle
Indicates that one entity incorporates or exhibits a crossover style derived from or blending characteristics of another entity.
-
D.
featuresCrossShape
Indicates that something has a form, pattern, or configuration resembling a cross shape.
-
E.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: April 29, 2026, 9:10 p.m.