Triple
T185696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman law |
E3974
|
entity |
| Predicate | revivedIn |
P529
|
FINISHED |
| Object | medieval universities |
—
|
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: medieval universities | Statement: [Roman law, revivedIn, medieval universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivedIn Context triple: [Roman law, revivedIn, medieval universities]
-
A.
revivalMovement
Indicates a religious or spiritual campaign aimed at renewing or intensifying faith, devotion, or practice among a group of people.
-
B.
reconstructedAfter
chosen
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
C.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
D.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.