Triple
T33522998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riegelsville Inn |
E858558
|
entity |
| Predicate | isLocallyKnownFor |
P65126
|
FINISHED |
| Object | historic ambiance |
—
|
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: historic ambiance | Statement: [Riegelsville Inn, isLocallyKnownFor, historic ambiance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocallyKnownFor Context triple: [Riegelsville Inn, isLocallyKnownFor, historic ambiance]
-
A.
knownIn
chosen
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
isKnownPrimarilyByName
Indicates that an entity is chiefly recognized or identified by its name rather than by other attributes or characteristics.
-
C.
segmentKnownFor
Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
-
D.
isLessKnownFor
Indicates that one entity is recognized or associated with something to a lesser degree than another entity is.
-
E.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:39 a.m.