Triple
T1188670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wave Swinger |
E25305
|
entity |
| Predicate | hasRestraintType |
P22102
|
FINISHED |
| Object | lap chain |
—
|
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: lap chain | Statement: [Wave Swinger, hasRestraintType, lap chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestraintType Context triple: [Wave Swinger, hasRestraintType, lap chain]
-
A.
restraintType
chosen
Indicates the specific kind or method of restraint applied in a given situation or relationship.
-
B.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.