Triple
T9068703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Recording Code |
E217307
|
entity |
| Predicate | registrantCodeLength |
P33158
|
FINISHED |
| Object | 3 characters |
—
|
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: 3 characters | Statement: [International Standard Recording Code, registrantCodeLength, 3 characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrantCodeLength Context triple: [International Standard Recording Code, registrantCodeLength, 3 characters]
-
A.
registrantCode
Indicates the unique code assigned to a registrant that identifies them within a registration or cataloging system.
-
B.
identifierLength
chosen
Indicates the length or number of characters in an entity’s identifier.
-
C.
typicalNameLength
Indicates the usual or characteristic number of characters in the names of entities in a given context.
-
D.
hasCategoryLengthRestriction
Indicates that there is a constraint on the allowable length of a category, such as its name, identifier, or structural size.
-
E.
hasNameLengthCategory
Indicates that an entity is associated with a classification describing the length of its name (e.g., short, medium, long).
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ba250819085fa49e0059d06c1 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.