Triple
T12753170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrenceville, New Jersey |
E304786
|
entity |
| Predicate | NRHPreferenceNumber |
P85770
|
FINISHED |
| Object | 78001774 |
—
|
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: 78001774 | Statement: [Lawrenceville, New Jersey, NRHPreferenceNumber, 78001774]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NRHPreferenceNumber Context triple: [Lawrenceville, New Jersey, NRHPreferenceNumber, 78001774]
-
A.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
hasRecommendationNumber
chosen
Indicates that an entity is associated with a specific recommendation identified by a particular number.
-
C.
currentPreference
Indicates the option, choice, or setting that an entity presently favors over alternatives at this moment in time.
-
D.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
E.
numberInPreservation
Indicates that an entity has a specified quantity or count within a preservation context (such as items preserved, stored, or maintained).
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.