Triple
T1434092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Lightweight Title |
E30517
|
entity |
| Predicate | historicalRoundLength |
P11575
|
FINISHED |
| Object | 15 rounds in earlier eras |
—
|
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: 15 rounds in earlier eras | Statement: [World Lightweight Title, historicalRoundLength, 15 rounds in earlier eras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRoundLength Context triple: [World Lightweight Title, historicalRoundLength, 15 rounds in earlier eras]
-
A.
standardRoundLength
Indicates that there is a defined, typical duration assigned to a single round within a process, activity, or game.
-
B.
gameLength
Indicates the duration or total length of a game, typically measured in time or turns.
-
C.
gameLengthRule
Indicates a rule that specifies how long a game is allowed or required to last.
-
D.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
-
E.
roundCount
chosen
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
- 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_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. |
Created at: March 1, 2026, 8 p.m.