Triple
T15353567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldwell Township, New Jersey |
E367113
|
entity |
| Predicate | hadPrimaryLandUse |
P14072
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Caldwell Township, New Jersey, hadPrimaryLandUse, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrimaryLandUse Context triple: [Caldwell Township, New Jersey, hadPrimaryLandUse, residential]
-
A.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
B.
primaryLandUse
chosen
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
C.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
D.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2a8e88819093e4b7479b2c80cd |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.