Triple
T22300364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Married Joan |
E551236
|
entity |
| Predicate | hasOpeningCreditsBilling |
P56245
|
FINISHED |
| Object | Joan Davis |
—
|
NE NERFINISHED |
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: Joan Davis | Statement: [I Married Joan, hasOpeningCreditsBilling, Joan Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningCreditsBilling Context triple: [I Married Joan, hasOpeningCreditsBilling, Joan Davis]
-
A.
hasOpeningCreditsUsage
chosen
Indicates that something is used or appears specifically in the opening credits of a work.
-
B.
hasEndCreditsOrder
Indicates the sequence or position in which entities are listed in the end credits of a work.
-
C.
hasOpeningScene
Indicates that a work (such as a film, show, or story) possesses a specific initial scene that begins or introduces its narrative.
-
D.
hasOpeningFeature
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
-
E.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572399148190853c4e91fcf9f38c |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.