Triple
T19013246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel |
E465278
|
entity |
| Predicate | frequencyCategoryLate20thCenturyEnglish |
P134124
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Rachel, frequencyCategoryLate20thCenturyEnglish, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyCategoryLate20thCenturyEnglish Context triple: [Rachel, frequencyCategoryLate20thCenturyEnglish, high]
-
A.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
B.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
C.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
D.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
E.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a9bac8819093f9af57000667b0 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.