Triple
T2200844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aileen Wuornos in Monster |
E50483
|
entity |
| Predicate | hasLegalOutcomeInFiction |
P13811
|
FINISHED |
| Object | arrest |
—
|
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: arrest | Statement: [Aileen Wuornos in Monster, hasLegalOutcomeInFiction, arrest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalOutcomeInFiction Context triple: [Aileen Wuornos in Monster, hasLegalOutcomeInFiction, arrest]
-
A.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
C.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
D.
stateInFiction
chosen
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
-
E.
hasReputationInFiction
Indicates that an entity is known or regarded in a particular way within fictional works or narratives.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa06bb4819092d7021358846e5f |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.