Triple
T13595815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 97 |
E324814
|
entity |
| Predicate | isRedevelopedFrom |
P62421
|
FINISHED |
| Object | former working pier |
—
|
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: former working pier | Statement: [Pier 97, isRedevelopedFrom, former working pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRedevelopedFrom Context triple: [Pier 97, isRedevelopedFrom, former working pier]
-
A.
developedFrom
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
B.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
C.
formerlyDevelopedBy
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
-
D.
redevelopmentFrom
chosen
Indicates that one entity is created or transformed as a result of redeveloping or repurposing another pre-existing entity.
-
E.
hasRedevelopedArea
Indicates that an entity has an area that has been improved, renovated, or rebuilt from its previous state.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.