Triple
T33933773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitoria's relectiones |
E869974
|
entity |
| Predicate | composedAt |
P59755
|
FINISHED |
| Object | University of Salamanca |
—
|
NE NERFINISHED |
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: University of Salamanca | Statement: [Vitoria's relectiones, composedAt, University of Salamanca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedAt Context triple: [Vitoria's relectiones, composedAt, University of Salamanca]
-
A.
dateOfComposition
Indicates the calendar date or time period when a particular work was created or composed.
-
B.
madeAt
chosen
Indicates the specific place or time at which something was created, produced, or manufactured.
-
C.
posedAt
Indicates that something (such as a question, challenge, or problem) is directed toward or presented to a particular target or context.
-
D.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
E.
compiledAt
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:49 a.m.