Triple
T29591259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donaldson Mountain |
E754165
|
entity |
| Predicate | hasListingNumber |
P191690
|
FINISHED |
| Object | 33 |
—
|
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: 33 | Statement: [Donaldson Mountain, hasListingNumber, 33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingNumber Context triple: [Donaldson Mountain, hasListingNumber, 33]
-
A.
hasListingSystem
Indicates that an entity is associated with or uses a particular system or mechanism for listing or cataloging items, entries, or information.
-
B.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
C.
isListing
Indicates that an entity functions as a listing, typically representing an item, service, or offering that is being presented, advertised, or made available.
-
D.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
E.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
- F. None of above. chosen
Provenance (4 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 28, 2026, 6:14 p.m.