Triple
T30834785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformation of Tour Bois-le-Prêtre, Paris |
E785329
|
entity |
| Predicate | preRenovationStoreys |
P170550
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Transformation of Tour Bois-le-Prêtre, Paris, preRenovationStoreys, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRenovationStoreys Context triple: [Transformation of Tour Bois-le-Prêtre, Paris, preRenovationStoreys, 16]
-
A.
postRefurbishmentNarrator
Indicates that a narrator is providing commentary or narration after a refurbishment or renovation has been completed.
-
B.
renovatedFrom
Indicates that one entity has been updated, improved, or restored by modifying or reworking an earlier version represented by another entity.
-
C.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
D.
renovationOccasion
Indicates the event, reason, or context that serves as the occasion for a renovation to take place.
-
E.
wasRenovatedFor
Indicates that an existing entity underwent renovation specifically to serve the needs, purposes, or use of another entity.
- F. None of above. chosen
Provenance (4 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6913cecbc8190a26e1b3233c0d842 |
completed | May 3, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:45 p.m.