Triple
T31999662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royan |
E817088
|
entity |
| Predicate | wasRebuiltInStyle |
P23767
|
FINISHED |
| Object | modernist architecture |
—
|
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: modernist architecture | Statement: [Royan, wasRebuiltInStyle, modernist architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRebuiltInStyle Context triple: [Royan, wasRebuiltInStyle, modernist architecture]
-
A.
rebuiltInStyle
chosen
Indicates that something has been reconstructed or renovated following the characteristics, design principles, or aesthetic conventions of a specified style.
-
B.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
-
C.
rebuiltFor
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
D.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
-
E.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fb2f48819095ee389b66f69b7c |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:14 a.m.