Triple
T22080040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millville Meteor |
E545624
|
entity |
| Predicate | isNicknamedAfterBirthplace |
P38200
|
FINISHED |
| Object | Millville, 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: Millville, New Jersey | Statement: [Millville Meteor, isNicknamedAfterBirthplace, Millville, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNicknamedAfterBirthplace Context triple: [Millville Meteor, isNicknamedAfterBirthplace, Millville, New Jersey]
-
A.
isInCityNicknamed
Indicates that one entity is located in a city that is known by a particular nickname.
-
B.
nicknamedFor
chosen
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
C.
homeCityLandmarkReferencedInNickname
Indicates that a landmark from a person's home city is mentioned or alluded to in their nickname.
-
D.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
E.
cityNamedAfter
Indicates that one city derives its name from or was named in honor of another entity, such as a person, place, or concept.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b56d5c8190aa825fe02e3ad917 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.