Triple
T37192210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Falls of the Passaic River |
E921486
|
entity |
| Predicate | townshipNamedAfter |
P21562
|
FINISHED |
| Object | Little Falls, New Jersey |
—
|
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: Little Falls, New Jersey | Statement: [Little Falls of the Passaic River, townshipNamedAfter, Little Falls, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townshipNamedAfter Context triple: [Little Falls of the Passaic River, townshipNamedAfter, Little Falls, New Jersey]
-
A.
hasPlaceNamedAfter
chosen
Indicates that one place is named in honor of or derived from the name of another place.
-
B.
usedAsTownNameFor
Indicates that something serves as the official or common name of a particular town.
-
C.
cityNamedAfter
Indicates that one city derives its name from or was named in honor of another entity, such as a person, place, or concept.
-
D.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby town.
-
E.
nicknameOfTown
Indicates that one entity is a nickname or informal name used to refer to a particular town.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.