Triple
T33226293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandelbaum family |
E850559
|
entity |
| Predicate | notablePlaceOnProperty |
P10233
|
FINISHED |
| Object | Mandelbaum Gate crossing |
E242647
|
NE 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: Mandelbaum Gate crossing | Statement: [Mandelbaum family, notablePlaceOnProperty, Mandelbaum Gate crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceOnProperty Context triple: [Mandelbaum family, notablePlaceOnProperty, Mandelbaum Gate crossing]
-
A.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
B.
notablePlace
chosen
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notablePropertyLocation
Indicates that a specific property or characteristic of an entity is notably associated with, or located in, a particular place.
-
D.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
- F. None of above.
Provenance (4 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35430b11248190b5f2addbb1981002 |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.