Triple
T1920005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Name Identifier |
E40103
|
entity |
| Predicate | includesCheckDigit |
P22178
|
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: [International Standard Name Identifier, includesCheckDigit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCheckDigit Context triple: [International Standard Name Identifier, includesCheckDigit, true]
-
A.
hasCheckDigit
chosen
Indicates that an identifier or code includes a calculated check digit used to verify its correctness or integrity.
-
B.
checkDigitAlgorithm
Indicates the algorithm or method used to compute or validate a check digit for an identifier or code.
-
C.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
D.
usesIntegrityCheck
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
E.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb213af0481909429ec971860a3fd |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.