Triple
T10408355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scollay Square |
E245322
|
entity |
| Predicate | currentPhysicalRemnant |
P44035
|
FINISHED |
| Object | largely none |
—
|
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: largely none | Statement: [Scollay Square, currentPhysicalRemnant, largely none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPhysicalRemnant Context triple: [Scollay Square, currentPhysicalRemnant, largely none]
-
A.
lastRemnantOf
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
B.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
C.
remnants
chosen
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
D.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
E.
isYoungerRemnantOf
Indicates that one entity is the surviving, younger portion or successor of another entity that existed earlier and has largely disappeared or transformed.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9f9b59881909797646fd8cd6a7e |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:09 p.m.