Triple
T29732051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Évora Cathedral |
E752352
|
entity |
| Predicate | styleTransition |
P36477
|
FINISHED |
| Object | Romanesque to Gothic |
—
|
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: Romanesque to Gothic | Statement: [Évora Cathedral, styleTransition, Romanesque to Gothic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleTransition Context triple: [Évora Cathedral, styleTransition, Romanesque to Gothic]
-
A.
styleTransitionRole
Indicates a role that an entity plays in enabling, guiding, or characterizing a change from one style or stylistic state to another.
-
B.
formsTransitionBetween
Indicates that one state, phase, or condition serves as an intermediate link or bridge leading from one distinct state, phase, or condition to another.
-
C.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
-
D.
transitionReason
Indicates the cause, motivation, or triggering factor behind a change from one state, status, or condition to another.
-
E.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 7:43 p.m.