Triple
T4616867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO standards |
E100888
|
entity |
| Predicate | arePublishedAs |
P23558
|
FINISHED |
| Object | ISO documents |
—
|
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: ISO documents | Statement: [ISO standards, arePublishedAs, ISO documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arePublishedAs Context triple: [ISO standards, arePublishedAs, ISO documents]
-
A.
publishedAs
chosen
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
B.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
-
C.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
-
D.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.