Triple
T19499539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weaver Square (redevelopment area) |
E487864
|
entity |
| Predicate | isEarmarkedFor |
P85702
|
FINISHED |
| Object | redevelopment |
—
|
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: redevelopment | Statement: [Weaver Square (redevelopment area), isEarmarkedFor, redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEarmarkedFor Context triple: [Weaver Square (redevelopment area), isEarmarkedFor, redevelopment]
-
A.
isEarmarked
chosen
Indicates that something has been specifically designated, reserved, or set aside for a particular purpose, use, or recipient.
-
B.
isOnReserve
Indicates that an entity is currently set aside or held in reserve, rather than being in regular or active use.
-
C.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
-
D.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
E.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6349462108190bb763b4e03bf000d |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.