Triple
T26527695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Courtenay family |
E670736
|
entity |
| Predicate | prominentInPeriod |
P24496
|
FINISHED |
| Object | Tudor period |
—
|
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: Tudor period | Statement: [English Courtenay family, prominentInPeriod, Tudor period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentInPeriod Context triple: [English Courtenay family, prominentInPeriod, Tudor period]
-
A.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
B.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
-
C.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
D.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
E.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:33 a.m.