Triple
T11224533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England 4000-footers |
E265660
|
entity |
| Predicate | hasTotalPeaks |
P48325
|
FINISHED |
| Object | 67 |
—
|
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: 67 | Statement: [New England 4000-footers, hasTotalPeaks, 67]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalPeaks Context triple: [New England 4000-footers, hasTotalPeaks, 67]
-
A.
numberOfPeaks
chosen
Indicates the count of distinct peak points or maximum values present within a given entity or dataset.
-
B.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
C.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
-
D.
hasPeakAround
Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
-
E.
hasSecondaryPeak
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ee15d4819087449058addef597 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.