Triple
T1508198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Tom |
E33949
|
entity |
| Predicate | hasFormerUse |
P29363
|
FINISHED |
| Object | site of Mount Tom Ski Area |
—
|
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: site of Mount Tom Ski Area | Statement: [Mount Tom, hasFormerUse, site of Mount Tom Ski Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerUse Context triple: [Mount Tom, hasFormerUse, site of Mount Tom Ski Area]
-
A.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
hasFormerService
Indicates that an entity previously provided a service to another entity but no longer does so.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
hasFirstDocumentedUse
Indicates that one entity is the earliest known or recorded instance in which the other entity was used or attested.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a8e2dd93dc8190a78443900e8d5564 |
completed | March 5, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a88728c150819095cdcdbfcabf4249 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a8e2dbc848819084eb0d50189fa967 |
completed | March 5, 2026, 1:56 a.m. |
Created at: March 4, 2026, 7:24 p.m.