Triple
T8641637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maarkedal |
E204664
|
entity |
| Predicate | hasNISCode |
P3943
|
FINISHED |
| Object | 45064 |
—
|
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: 45064 | Statement: [Maarkedal, hasNISCode, 45064]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNISCode Context triple: [Maarkedal, hasNISCode, 45064]
-
A.
hasNationalLocationCode
Indicates that an entity is associated with a specific national location code that identifies its location within a country’s coding system.
-
B.
hasONSCode
Indicates that an entity is associated with a specific code assigned by the Office for National Statistics (ONS) for identification or classification purposes.
-
C.
hasNISTDesignation
Indicates that an entity is assigned a specific designation or identifier defined by NIST (the National Institute of Standards and Technology).
-
D.
hasMunicipalityCode
chosen
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
E.
hasInn
Indicates that one entity possesses, operates, or is associated with an inn as part of its facilities or properties.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4795b07081908bfc9ebf35a50f07 |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.