Triple
T37452910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Fault |
E930714
|
entity |
| Predicate | mapScaleSignificance |
P34421
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Portland Fault, mapScaleSignificance, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapScaleSignificance Context triple: [Portland Fault, mapScaleSignificance, regional]
-
A.
mapScale
Indicates the ratio between distances on a map and the corresponding actual distances in the real world.
-
B.
mapScaleCategory
Indicates the classification of a map based on its scale range or level of detail.
-
C.
cartographicSignificance
chosen
Indicates the importance or relevance of something within the context of mapping or geographic representation.
-
D.
navigationSignificance
Indicates the degree to which something serves as a meaningful aid or reference point for determining or following a route or direction.
-
E.
significantScale
Indicates that the scale, size, or magnitude of something is notably large or important relative to a given context or standard.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.