Triple
T27401037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gray Peak |
E691841
|
entity |
| Predicate | withinList |
P31874
|
FINISHED |
| Object | Adirondack Forty-Sixers |
—
|
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: Adirondack Forty-Sixers | Statement: [Gray Peak, withinList, Adirondack Forty-Sixers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinList Context triple: [Gray Peak, withinList, Adirondack Forty-Sixers]
-
A.
includesList
Indicates that one entity contains or encompasses a specified list of other entities as its elements or members.
-
B.
listedWith
chosen
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
C.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
D.
listedInField
Indicates that something is included or recorded within a particular field, category, or area of information.
-
E.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:29 p.m.