Triple
T6563176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose window |
E153836
|
entity |
| Predicate | isCommonlyFoundIn |
P13132
|
FINISHED |
| Object | cathedrals |
—
|
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: cathedrals | Statement: [Rose window, isCommonlyFoundIn, cathedrals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyFoundIn Context triple: [Rose window, isCommonlyFoundIn, cathedrals]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
C.
cohabitsWith
Indicates that two entities live together in the same dwelling or shared residence.
-
D.
traditionallyFoundIn
chosen
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
E.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
- 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.