Triple
T37458249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild |
E930852
|
entity |
| Predicate | permitsArchetype |
P187888
|
FINISHED |
| Object | combo decks |
—
|
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: combo decks | Statement: [Wild, permitsArchetype, combo decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsArchetype Context triple: [Wild, permitsArchetype, combo decks]
-
A.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
B.
usesCharacterArchetype
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
C.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
D.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
E.
architectureCanUse
Indicates that a particular architecture is capable of employing, incorporating, or being built with a specified component, technique, or resource.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.