Triple
T15984487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomsburg, Pennsylvania |
E387657
|
entity |
| Predicate | isOnlyInState |
P19880
|
FINISHED |
| Object | only incorporated town in Pennsylvania |
—
|
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: only incorporated town in Pennsylvania | Statement: [Bloomsburg, Pennsylvania, isOnlyInState, only incorporated town in Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnlyInState Context triple: [Bloomsburg, Pennsylvania, isOnlyInState, only incorporated town in Pennsylvania]
-
A.
isOnlyCurrentThat
chosen
Indicates that the subject is the sole entity that currently satisfies or holds the specified condition, with no other concurrent instances.
-
B.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
C.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
-
D.
activeInState
Indicates that an entity is currently functioning, operating, or valid within a specified state or condition.
-
E.
isStateOwned
Indicates that an entity is owned or controlled by a government or state authority.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.