Triple
T28794641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi Towers development |
E727051
|
entity |
| Predicate | formerSiteName |
P196114
|
FINISHED |
| Object | Maison Centrale |
—
|
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: Maison Centrale | Statement: [Hanoi Towers development, formerSiteName, Maison Centrale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSiteName Context triple: [Hanoi Towers development, formerSiteName, Maison Centrale]
-
A.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
B.
formerSiteOwner
Indicates that one entity previously owned or controlled a particular site but no longer does so.
-
C.
formerName
Indicates that an entity was previously known by a different name in the past.
-
D.
formerOrganization
Indicates that an entity was previously affiliated with or employed by a given organization, but is no longer associated with it.
-
E.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
- F. None of above. chosen
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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
| PDg | Predicate description generation | batch_69fe08d1b3f881908eccb74cb0d246dc |
completed | May 8, 2026, 4:01 p.m. |
Created at: April 28, 2026, 6:24 a.m.