Triple
T32876814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mad Genius (1931 film) |
E840948
|
entity |
| Predicate | hasPreCodeContent |
P203146
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Mad Genius (1931 film), hasPreCodeContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreCodeContent Context triple: [The Mad Genius (1931 film), hasPreCodeContent, true]
-
A.
hasPreCodeStatus
Indicates that an entity held a specific code-related status or classification at some earlier point in time.
-
B.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
C.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
D.
hasFormerCode
Indicates that an entity was previously identified or referenced by an earlier code that is no longer current.
-
E.
hasPrelude
Indicates that one entity includes or is associated with a preceding introductory section or preface to another entity.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01289f781481908f3788f8a719f2f4 |
completed | May 11, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a012823c7248190961e20be48dd6246 |
completed | May 11, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_6a01289ecf7481908802642bb4399ac0 |
completed | May 11, 2026, 12:53 a.m. |
Created at: May 1, 2026, 1:18 a.m.