Triple
T2537777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Register of Historic Places |
E56309
|
entity |
| Predicate | hasTypeOfDesignation |
P974
|
FINISHED |
| Object | historic place designation |
—
|
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: historic place designation | Statement: [New Jersey Register of Historic Places, hasTypeOfDesignation, historic place designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDesignation Context triple: [New Jersey Register of Historic Places, hasTypeOfDesignation, historic place designation]
-
A.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
C.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
D.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
E.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.