Triple
T15244311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norge 1:50 000 map series |
E364339
|
entity |
| Predicate | detailLevel |
P109501
|
FINISHED |
| Object | large-scale |
—
|
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: large-scale | Statement: [Norge 1:50 000 map series, detailLevel, large-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detailLevel Context triple: [Norge 1:50 000 map series, detailLevel, large-scale]
-
A.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
-
B.
representationLevel
Indicates the degree or layer at which something stands in for, models, or symbolizes something else (e.g., more concrete vs. more abstract representation).
-
C.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
D.
granularityLevel
chosen
Indicates the degree of detail or resolution at which something is specified, measured, or analyzed within a given context.
-
E.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f306f08190be448b215d6c9b6c |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.