Triple
T19073263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 843 |
E466843
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | ISO 259 |
—
|
NE NERFINISHED |
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: ISO 259 | Statement: [ISO 843, relatedTo, ISO 259]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 259 Context triple: [ISO 843, relatedTo, ISO 259]
-
A.
ISO 259
chosen
ISO 259 is an international standard that defines a systematic method for the transliteration of Hebrew characters into the Latin alphabet.
-
B.
ISO 259-3
ISO 259-3 is a part of the ISO 259 standard that specifies a system for the transliteration of Hebrew characters into Latin script.
-
C.
ISO 23950
ISO 23950 is an international standard that defines the Z39.50 client-server protocol for searching and retrieving information from remote databases in a networked environment.
-
D.
ISO 999
ISO 999 is an international standard that specifies rules for the content, organization, and presentation of indexes in books, periodicals, and other written documents.
-
E.
ISO 28500
ISO 28500 is the international standard that defines the WARC (Web ARChive) file format used for storing and preserving web crawls and other digital resources.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e1ce5881908367424c89d73feb |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 10, 2026, 12:04 p.m.