Triple
T6184773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iban language |
E138028
|
entity |
| Predicate | isStandardized |
P8040
|
FINISHED |
| Object | partially |
—
|
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: partially | Statement: [Iban language, isStandardized, partially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardized Context triple: [Iban language, isStandardized, partially]
-
A.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
E.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c061020d148190ae2edf2b363f1e24 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.