Triple
T1632140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Standard |
E35278
|
entity |
| Predicate | hasIdentifierScheme |
P1285
|
FINISHED |
| Object | STD number |
—
|
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: STD number | Statement: [Internet Standard, hasIdentifierScheme, STD number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentifierScheme Context triple: [Internet Standard, hasIdentifierScheme, STD number]
-
A.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
B.
hasCodeScheme
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
E.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.