Triple
T1434089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Lightweight Title |
E30517
|
entity |
| Predicate | requiresWeighIn |
P28482
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [World Lightweight Title, requiresWeighIn, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWeighIn Context triple: [World Lightweight Title, requiresWeighIn, true]
-
A.
requiresCheckIn
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
-
B.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
-
C.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
-
D.
requiresCheckOut
Indicates that one entity must be formally checked out or borrowed before it can be used, accessed, or taken by another entity.
-
E.
requiredRiderOath
Indicates that an individual is obligated to take or uphold a specific rider’s oath as a condition for participation or status.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.