Triple
T33567380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Princeton |
E859793
|
entity |
| Predicate | hadPostalDesignation |
P19163
|
FINISHED |
| Object | Princeton, NJ |
—
|
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, NJ | Statement: [Borough of Princeton, hadPostalDesignation, Princeton, NJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPostalDesignation Context triple: [Borough of Princeton, hadPostalDesignation, Princeton, NJ]
-
A.
postalServiceDesignation
chosen
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
B.
hadPostalAbbreviation
Indicates that an entity was associated with a specific official postal abbreviation at some time.
-
C.
postalTheme
Indicates that something is related to, characterized by, or themed around postal services, mail, or mailing systems.
-
D.
hasPostalFeature
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
E.
hadPostOffice
Indicates that a place or entity possessed or was served by an official post office facility.
- 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_69f6f740ee548190a73daee3321d8264 |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.