Triple
T22797310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romilda |
E564283
|
entity |
| Predicate | hasTimePeriodOfCreation |
P116819
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Romilda, hasTimePeriodOfCreation, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfCreation Context triple: [Romilda, hasTimePeriodOfCreation, 18th century]
-
A.
timeSpanOfCreation
chosen
Indicates the period of time during which the creation of an entity took place.
-
B.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
C.
createdAtRequestOf
Indicates that something was created specifically in response to, or because of, a particular request.
-
D.
effectiveCreationDate
Indicates the date on which something actually comes into effect or becomes valid, as opposed to when it was merely created or recorded.
-
E.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd9b3c0819096050f43a829ec0d |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.