Triple
T24169483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughrabi Gate |
E599086
|
entity |
| Predicate | nearbyFormerQuarter |
P98811
|
FINISHED |
| Object | Mughrabi Quarter |
—
|
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: Mughrabi Quarter | Statement: [Mughrabi Gate, nearbyFormerQuarter, Mughrabi Quarter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyFormerQuarter Context triple: [Mughrabi Gate, nearbyFormerQuarter, Mughrabi Quarter]
-
A.
locatedNearFormer
chosen
Indicates that one entity is situated close to another entity that previously occupied a nearby or the same location.
-
B.
formerNeighborhood
Indicates that an entity was previously located in or associated with a particular neighborhood but is no longer situated there.
-
C.
nearbyFormerStation
Indicates that one entity is located close to another entity that used to be a station but is no longer in operation.
-
D.
hasFormerNearbyLandmark
Indicates that an entity previously had a nearby landmark that no longer exists or no longer holds the same status or relevance.
-
E.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.