Triple
T31201183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikon Base Pass |
E795478
|
entity |
| Predicate | hasMoreRestrictionsThan |
P194813
|
FINISHED |
| Object | Ikon Pass |
—
|
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: Ikon Pass | Statement: [Ikon Base Pass, hasMoreRestrictionsThan, Ikon Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoreRestrictionsThan Context triple: [Ikon Base Pass, hasMoreRestrictionsThan, Ikon Pass]
-
A.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
B.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
C.
hasTypeOfRestriction
Indicates that an entity is subject to a specific kind or category of restriction that limits its use, access, or behavior.
-
D.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
-
E.
hadRestrictionsOn
Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: April 29, 2026, 9:09 p.m.