Triple
T31023279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Cervera |
E790504
|
entity |
| Predicate | significantBuildingStart |
P77727
|
FINISHED |
| Object | 1718 |
—
|
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: 1718 | Statement: [University of Cervera, significantBuildingStart, 1718]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantBuildingStart Context triple: [University of Cervera, significantBuildingStart, 1718]
-
A.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
B.
significantBuildingWithin
Indicates that a building of notable importance is located inside the boundaries of another specified area or structure.
-
C.
monumentConstructionStart
chosen
Indicates the date or time when the construction of a monument was begun.
-
D.
oldestBuildingDate
Indicates the calendar date on which the earliest or first-constructed building in a given set or area was built or completed.
-
E.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:58 p.m.