Triple
T28106634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old City of Shanghai |
E710380
|
entity |
| Predicate | wallStatus |
P125898
|
FINISHED |
| Object | most walls demolished in late 19th and early 20th centuries |
—
|
LITERAL 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: most walls demolished in late 19th and early 20th centuries | Statement: [Old City of Shanghai, wallStatus, most walls demolished in late 19th and early 20th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallStatus Context triple: [Old City of Shanghai, wallStatus, most walls demolished in late 19th and early 20th centuries]
-
A.
wandStatus
Indicates the current condition or operational state of a wand in relation to its use or functionality.
-
B.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
-
C.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
D.
wallCharacteristic
chosen
Indicates that a specified characteristic or property is attributed to a wall.
-
E.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c50dc88190a93952b9b87eb588 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:08 p.m.