Triple
T34348754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landis Township |
E881507
|
entity |
| Predicate | historicLocationNowWithin |
P50232
|
FINISHED |
| Object | Vineland, New Jersey |
—
|
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: Vineland, New Jersey | Statement: [Landis Township, historicLocationNowWithin, Vineland, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicLocationNowWithin Context triple: [Landis Township, historicLocationNowWithin, Vineland, New Jersey]
-
A.
historicLocation
Indicates that an entity is situated in or associated with a place of historical significance.
-
B.
historicalLocationNowIn
chosen
Indicates that an entity’s historical location is now situated within the boundaries of another, current geographic or political entity.
-
C.
historicAreaNowIn
Indicates that an area which was historically part of one place is now located within the boundaries of another place.
-
D.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
E.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 1, 2026, 1:58 a.m.