Triple
T13721714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ave Regina Caelorum |
E329052
|
entity |
| Predicate | hasApproximateOriginPeriod |
P38044
|
FINISHED |
| Object | Middle Ages |
—
|
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: Middle Ages | Statement: [Ave Regina Caelorum, hasApproximateOriginPeriod, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOriginPeriod Context triple: [Ave Regina Caelorum, hasApproximateOriginPeriod, Middle Ages]
-
A.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
B.
timePeriodOrigin
chosen
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
C.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
D.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
hasHistoricalOriginInYear
Indicates that something first originated, began, or came into existence in a specified calendar year.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f3b46481909ceedfa78e9ca92b |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.