Triple
T6189003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Palisades |
E138137
|
entity |
| Predicate | threatenedHistoricallyBy |
P14802
|
FINISHED |
| Object | quarrying and development |
—
|
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: quarrying and development | Statement: [New Jersey Palisades, threatenedHistoricallyBy, quarrying and development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatenedHistoricallyBy Context triple: [New Jersey Palisades, threatenedHistoricallyBy, quarrying and development]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
historicalThreat
chosen
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
C.
heritageThreat
Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
-
D.
historicalPeriodOfGreatestDanger
Indicates the time period in which an entity faced its highest level of risk, threat, or vulnerability.
-
E.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062192c5481909eb41f8c5d1208a3 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.