Triple
T4078206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-23 |
E87414
|
entity |
| Predicate | hasStandardNumber |
P4626
|
FINISHED |
| Object | S-23 |
—
|
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: S-23 | Statement: [S-23, hasStandardNumber, S-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardNumber Context triple: [S-23, hasStandardNumber, S-23]
-
A.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
B.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
C.
standardNumber
chosen
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4e95b08190bd1ee8f6d3a9613c |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.