Triple
T7902861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardroom Estate |
E183496
|
entity |
| Predicate | timeOfMajorRedevelopment |
P54016
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Cardroom Estate, timeOfMajorRedevelopment, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorRedevelopment Context triple: [Cardroom Estate, timeOfMajorRedevelopment, early 2000s]
-
A.
majorRedevelopmentPeriod
chosen
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
B.
redevelopmentStartDate
Indicates the date on which a redevelopment project or process officially begins.
-
C.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
D.
redevelopmentEnd
Indicates the point in time or event at which a redevelopment process or project is considered completed or ceases.
-
E.
hasRedevelopmentProgram
Indicates that an entity is subject to or involved in a planned process of redevelopment, typically through an organized program or initiative.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a41b0fc81909890f2e4f432a5cf |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.