Triple
T22996852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Case of the Negligent Nymph |
E572520
|
entity |
| Predicate | hasFictionalProfessionOfLead |
P34569
|
FINISHED |
| Object | lawyer |
—
|
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: lawyer | Statement: [The Case of the Negligent Nymph, hasFictionalProfessionOfLead, lawyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalProfessionOfLead Context triple: [The Case of the Negligent Nymph, hasFictionalProfessionOfLead, lawyer]
-
A.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
B.
hasFictionalProfessionLevel
Indicates that an entity holds a fictional or imagined profession at a specified level, rank, or degree of expertise.
-
C.
fictionalOccupation
chosen
Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity within a fictional context.
-
D.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
-
E.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f452b48190951fc5dde56c1bb2 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.