Triple
T18724928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WARC |
E457874
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | ISO 28500:2017 |
—
|
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 28500:2017 | Statement: [WARC, governedBy, ISO 28500:2017]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 28500:2017 Context triple: [WARC, governedBy, ISO 28500:2017]
-
A.
ISO 28500
chosen
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.
-
B.
ISO/IEC 27050
ISO/IEC 27050 is an international standard that provides guidelines and requirements for managing electronic discovery (e-discovery) within information security and governance frameworks.
-
C.
ISO/IEC 30170
ISO/IEC 30170 is an international standard that formally specifies the Ruby programming language.
-
D.
ISO/IEC 24748
ISO/IEC 24748 is an international standard that provides guidance on the application and management of systems and software life cycle processes defined in standards such as ISO/IEC 15288.
-
E.
ISO/IEC 19464
ISO/IEC 19464 is the international standard that specifies the Advanced Message Queuing Protocol (AMQP) for interoperable, message-oriented middleware communication.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.