Triple
T31486240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine Marten Lodge |
E803283
|
entity |
| Predicate | isMainLodgeOf |
P39867
|
FINISHED |
| Object | Mount Bachelor ski area |
—
|
NE NERFINISHED |
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: Mount Bachelor ski area | Statement: [Pine Marten Lodge, isMainLodgeOf, Mount Bachelor ski area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainLodgeOf Context triple: [Pine Marten Lodge, isMainLodgeOf, Mount Bachelor ski area]
-
A.
isMainBuildingOf
chosen
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
B.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
C.
hasHindquartersOf
Indicates that one entity possesses or exhibits the hindquarters characteristic or form of another entity.
-
D.
isMainConcourseOf
Indicates that one concourse serves as the primary or central concourse within a larger facility or complex.
-
E.
hasMainEdifice
Indicates that an entity possesses or is associated with a primary or principal building or 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:35 p.m.