Triple
T33567427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton Township |
E859794
|
entity |
| Predicate | containedPlace |
P6528
|
FINISHED |
| Object | Princeton Battlefield State Park |
—
|
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: Princeton Battlefield State Park | Statement: [Princeton Township, containedPlace, Princeton Battlefield State Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedPlace Context triple: [Princeton Township, containedPlace, Princeton Battlefield State Park]
-
A.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
B.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
C.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
D.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
E.
placesWithin
chosen
Indicates that one place or area is located entirely inside the boundaries of another place or area.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: May 1, 2026, 1:40 a.m.