Triple
T33937819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Savage |
E870081
|
entity |
| Predicate | placeOfNotability |
P3858
|
FINISHED |
| Object | Savage, Maryland region |
—
|
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: Savage, Maryland region | Statement: [John Savage, placeOfNotability, Savage, Maryland region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfNotability Context triple: [John Savage, placeOfNotability, Savage, Maryland region]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
D.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
E.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 1:49 a.m.