Triple
T22513985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eircode |
E556594
|
entity |
| Predicate | formatPattern |
P5329
|
FINISHED |
| Object | A99 A9A9 |
—
|
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: A99 A9A9 | Statement: [Eircode, formatPattern, A99 A9A9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatPattern Context triple: [Eircode, formatPattern, A99 A9A9]
-
A.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
B.
notationPattern
chosen
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
C.
formatLevel
Indicates the degree or style in which something is formatted or structured.
-
D.
observancePattern
Indicates how an action, rule, or practice is regularly carried out or followed over time, such as its schedule, frequency, or customary pattern of observance.
-
E.
formatAfter
Indicates that one entity’s format or structural arrangement is derived from, follows, or is applied subsequent to another entity’s format.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d62bea48190aaf34aa93bb3f67b |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.