Triple
T36086746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freshmen Adjustment 2 |
E1043804
|
entity |
| Predicate | hasUnofficialArtwork |
P193627
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Freshmen Adjustment 2, hasUnofficialArtwork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnofficialArtwork Context triple: [Freshmen Adjustment 2, hasUnofficialArtwork, yes]
-
A.
hasOfficialArtwork
Indicates that an entity is associated with an officially sanctioned piece of artwork representing it.
-
B.
hasUnofficialRelease
Indicates that an entity has a release or version that exists or is distributed outside of official or formally recognized channels.
-
C.
hasUnofficialStatus
Indicates that an entity holds a status or recognition that is not formally authorized, sanctioned, or officially recognized.
-
D.
hasNotableCoverArtist
Indicates that an entity has a cover (e.g., of a book, album, or publication) created by a cover artist who is considered notable.
-
E.
hasNotableWorkDepiction
Indicates that an entity has a notable work in which it is depicted or represented.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:08 p.m.