Triple
T26787689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merion Square |
E670431
|
entity |
| Predicate | hasPostalSuccessor |
P181034
|
FINISHED |
| Object | Gladwyne, Pennsylvania |
E177713
|
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: Gladwyne, Pennsylvania | Statement: [Merion Square, hasPostalSuccessor, Gladwyne, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalSuccessor Context triple: [Merion Square, hasPostalSuccessor, Gladwyne, Pennsylvania]
-
A.
hasLegalSuccessor
Indicates that one entity is the legally recognized successor or inheritor of another entity’s rights, obligations, or status.
-
B.
hasCitySuccessor
Indicates that one city is the successor or replacement of another city, typically in terms of status, function, or administrative role.
-
C.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
D.
hasSuccessorShip
Indicates that one entity is the ship that follows or replaces another ship in a sequence or lineage.
-
E.
hasOfficialSuccessorName
Indicates that an entity has an officially designated successor identified by a specific name.
- F. None of above. chosen
Provenance (5 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12a7b03a10819080131ba156020984 |
completed | May 24, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 27, 2026, 4:14 a.m.