Triple
T10635025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamesburg, New Jersey |
E250556
|
entity |
| Predicate | isIncorporatedSettlement |
P19845
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jamesburg, New Jersey, isIncorporatedSettlement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncorporatedSettlement Context triple: [Jamesburg, New Jersey, isIncorporatedSettlement, yes]
-
A.
isIncorporatedPlace
chosen
Indicates that a location is a legally established, self-governing municipal entity (such as a city, town, or village) recognized as an incorporated place.
-
B.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
-
C.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
D.
isRuralSettlement
Indicates that a settlement is located in a rural area, typically characterized by low population density and limited urban infrastructure.
-
E.
hasCityStatusSettlement
Indicates that a settlement possesses official recognition or designation as a city.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfac70f481908363f9ac0b651fbe |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:03 p.m.