Triple
T20615079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 18774 |
E506544
|
entity |
| Predicate | identificationSchemeType |
P95414
|
FINISHED |
| Object | name-based identification scheme |
—
|
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: name-based identification scheme | Statement: [ISO 18774, identificationSchemeType, name-based identification scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identificationSchemeType Context triple: [ISO 18774, identificationSchemeType, name-based identification scheme]
-
A.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
B.
designationScheme
chosen
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
C.
typeOfIdentity
Indicates the specific category or nature of identity that characterizes or defines an entity within a given context.
-
D.
identifierTypeManaged
Indicates that one entity is responsible for administering or controlling the type or scheme of identifiers used for another entity.
-
E.
identityStoredIn
Indicates that an entity’s identity information is kept or recorded within another entity or storage medium.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadaf47881909e93efb535c6c1e3 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.