Triple
T30061362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colton Point State Park |
E763895
|
entity |
| Predicate | nicknameOfView |
P109144
|
FINISHED |
| Object | Grand Canyon of Pennsylvania |
—
|
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: Grand Canyon of Pennsylvania | Statement: [Colton Point State Park, nicknameOfView, Grand Canyon of Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameOfView Context triple: [Colton Point State Park, nicknameOfView, Grand Canyon of Pennsylvania]
-
A.
viewNickname
Indicates that one entity views or displays the nickname associated with another entity.
-
B.
nicknameOfObject
chosen
Indicates that one entity is used as an informal or alternative name (nickname) for another entity.
-
C.
nicknameOfProduct
Indicates that one term is used as an informal or alternative name (nickname) for a particular product.
-
D.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
E.
namedAs
Indicates that one entity is given, known by, or referred to using the name 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca34d4081909ea4b2b02523d46a |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:58 p.m.