Triple
T341752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Book Number |
E6851
|
entity |
| Predicate | 10DigitInUseUntil |
P6544
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [International Standard Book Number, 10DigitInUseUntil, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 10DigitInUseUntil Context triple: [International Standard Book Number, 10DigitInUseUntil, 2006]
-
A.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
B.
retiredNumbersCount
Indicates the number of jersey or identification numbers that have been officially retired from use.
-
C.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
retiredNumbers
Indicates that a team has officially retired a specific player’s jersey number, taking it out of regular use in honor of that player.
-
E.
retiredNumber
Indicates that an entity (typically a team or organization) has formally withdrawn a specific number from future use, usually to honor a particular individual or achievement associated with that number.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae611f88190955fbebe2b01835b |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95197fc8190820e8ebd0d7d27fa |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.