Triple
T30798064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grim |
E784285
|
entity |
| Predicate | reasonBound |
P188889
|
FINISHED |
| Object | lost limbo contest |
—
|
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: lost limbo contest | Statement: [Grim, reasonBound, lost limbo contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonBound Context triple: [Grim, reasonBound, lost limbo contest]
-
A.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
-
B.
oftenBoundIn
Indicates that one entity is frequently enclosed, packaged, or contained within another entity.
-
C.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
D.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
E.
bounded
Indicates that one entity is spatially or conceptually enclosed, delimited, or constrained by another.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 29, 2026, 8:42 p.m.