Triple
T35526733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-1 |
E1026690
|
entity |
| Predicate | rulesLimit |
P91382
|
FINISHED |
| Object | clinching |
—
|
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: clinching | Statement: [K-1, rulesLimit, clinching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesLimit Context triple: [K-1, rulesLimit, clinching]
-
A.
rateConstraint
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
B.
definesLimitOf
chosen
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
C.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
D.
visitorLimit
Indicates a constraint specifying the maximum number of visitors allowed for a given entity or context.
-
E.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.