Triple
T19965030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Poetess |
E479908
|
entity |
| Predicate | appliedInEra |
P36703
|
FINISHED |
| Object | modern scholarship |
—
|
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: modern scholarship | Statement: [The Poetess, appliedInEra, modern scholarship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedInEra Context triple: [The Poetess, appliedInEra, modern scholarship]
-
A.
appliesToEra
chosen
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
E.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc4417c8190912f3d85fd7a5a32 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.