Triple
T4918109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splendor |
E110395
|
entity |
| Predicate | circulatedFrom |
P60017
|
FINISHED |
| Object | late 13th century |
—
|
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: late 13th century | Statement: [Splendor, circulatedFrom, late 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulatedFrom Context triple: [Splendor, circulatedFrom, late 13th century]
-
A.
circulatedAs
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
B.
originatedInDenomination
Indicates that an entity began or was founded within a particular religious denomination.
-
C.
hadCirculationIn
Indicates that an entity (such as a publication or medium) had its copies distributed or circulated within a specified location or region.
-
D.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
E.
originallyGivenTo
Indicates that something was first transferred, assigned, or presented to a particular recipient before any later changes in ownership or status.
- F. None of above. chosen
Provenance (4 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa760448190946401b4b21ea8b7 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.