Triple
T31446000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chick-A-Pin Hill |
E802187
|
entity |
| Predicate | iconicView |
P171883
|
FINISHED |
| Object | visible from multiple lands in the park |
—
|
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: visible from multiple lands in the park | Statement: [Chick-A-Pin Hill, iconicView, visible from multiple lands in the park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconicView Context triple: [Chick-A-Pin Hill, iconicView, visible from multiple lands in the park]
-
A.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
B.
iconOf
Indicates that one entity serves as a symbolic or representative image or emblem of another entity.
-
C.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
D.
iconographicVariant
Indicates that one representation is an alternative or variant visual depiction of another within an iconographic tradition or system.
-
E.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:09 p.m.