Triple
T28980388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Fun Night |
E734529
|
entity |
| Predicate | leadCharacterWorkplace |
P76778
|
FINISHED |
| Object | Manhattan law firm |
—
|
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: Manhattan law firm | Statement: [Super Fun Night, leadCharacterWorkplace, Manhattan law firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterWorkplace Context triple: [Super Fun Night, leadCharacterWorkplace, Manhattan law firm]
-
A.
workCharacter
Indicates that a person is a fictional or narrative character appearing in a particular creative work.
-
B.
workBasedOnThisCharacter
Indicates that a creative work is based on, inspired by, or derived from the referenced character.
-
C.
employerInPlot
Indicates that one entity serves as the employer of another within the context of a specific plot or storyline.
-
D.
workLocationOfFictionalCharacter
chosen
Indicates the place or organization where a fictional character is depicted as working within their narrative context.
-
E.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee362b081909decc8d1aa60ecab |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:11 a.m.