Triple
T28055592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Park Inn vicinity |
E708957
|
entity |
| Predicate | hasCoreStructure |
P49632
|
FINISHED |
| Object | National Park Inn |
—
|
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: National Park Inn | Statement: [National Park Inn vicinity, hasCoreStructure, National Park Inn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreStructure Context triple: [National Park Inn vicinity, hasCoreStructure, National Park Inn]
-
A.
hasCore
chosen
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreExtensionStructure
Indicates that one entity possesses or is characterized by a core structure that has been extended or augmented beyond its basic form.
-
C.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
D.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: April 27, 2026, 8:36 p.m.