Triple
T15622703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pencey Prep |
E375596
|
entity |
| Predicate | fictionalFoundingYear |
P16819
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Pencey Prep, fictionalFoundingYear, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalFoundingYear Context triple: [Pencey Prep, fictionalFoundingYear, 1888]
-
A.
foundedInFictionalYear
chosen
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
B.
fictionalBirthYear
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
-
C.
foundedByFictional
Indicates that an entity (such as an organization, place, or group) was established or created by a fictional character or entity.
-
D.
fictionalCenturyOfOrigin
Indicates the fictional century in which an entity is depicted as having originated or first appeared within its narrative world.
-
E.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9cfd94819091459aa17a002eaf |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.