Triple
T614588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Catcher in the Rye |
E12174
|
entity |
| Predicate | hasCensorshipHistory |
P17134
|
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, hasCensorshipHistory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCensorshipHistory Context triple: [The Catcher in the Rye, hasCensorshipHistory, true]
-
A.
hasWritingHistory
Indicates that an entity has a recorded history or log of its writing-related actions, changes, or authored content over time.
-
B.
hasDisputeHistory
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
C.
hasHistoricalInterruptions
Indicates that the continuity of an event, process, or relationship has been broken by one or more distinct interruptions over time.
-
D.
hasInflationHistory
Indicates that an entity is associated with a recorded or known pattern of inflation over time.
-
E.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
- 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.