Triple
T19917392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolean style |
E478699
|
entity |
| Predicate | hasAssociatedPeriod |
P123846
|
FINISHED |
| Object | reign of Charles II of England |
—
|
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: reign of Charles II of England | Statement: [Carolean style, hasAssociatedPeriod, reign of Charles II of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedPeriod Context triple: [Carolean style, hasAssociatedPeriod, reign of Charles II of England]
-
A.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
B.
appliedDuringPeriod
chosen
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
C.
hasSubPeriod
Indicates that a time period is composed of or contains another, more specific time period as a subordinate part.
-
D.
hasAssociatedYear
Indicates that an entity is linked to a specific year that is relevant to it (e.g., creation, occurrence, or reference year).
-
E.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65995bd60819097cfad003dd29731 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.