Triple
T6563214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose window |
E153836
|
entity |
| Predicate | isConstructedWith |
P23101
|
FINISHED |
| Object | stone framework |
—
|
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: stone framework | Statement: [Rose window, isConstructedWith, stone framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConstructedWith Context triple: [Rose window, isConstructedWith, stone framework]
-
A.
canBeConstructedWith
chosen
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
B.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
C.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
D.
isConstructive
Indicates that an action, behavior, or contribution has a positive, helpful, or improvement-oriented effect on a situation or outcome.
-
E.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.