Triple
T5083063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpe Diem (Uno expansion) |
E114569
|
entity |
| Predicate | adds |
P4097
|
FINISHED |
| Object | new 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: new cards | Statement: [Carpe Diem (Uno expansion), adds, new cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adds Context triple: [Carpe Diem (Uno expansion), adds, new cards]
-
A.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
B.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
C.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
E.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7517af308190bab5507a9344bf68 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.