Triple
T614590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Catcher in the Rye |
E12174
|
entity |
| Predicate | consideredClassic |
P17136
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Catcher in the Rye, consideredClassic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredClassic Context triple: [The Catcher in the Rye, consideredClassic, true]
-
A.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
B.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
C.
traditionalTitle
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
D.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
E.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0a0f588190b953fdb585263307 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.