Triple
T18750186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 22301 |
E458505
|
entity |
| Predicate | followsStructure |
P133404
|
FINISHED |
| Object | Annex SL high-level structure |
—
|
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: Annex SL high-level structure | Statement: [ISO 22301, followsStructure, Annex SL high-level structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsStructure Context triple: [ISO 22301, followsStructure, Annex SL high-level structure]
-
A.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
B.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
C.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
D.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
E.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
- F. None of above. chosen
Provenance (4 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ec71cc8190bb6d3fa6cca6dc8c |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.