Triple
T37623957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born in a Trunk |
E936149
|
entity |
| Predicate | featuredInTitleCharacter |
P69306
|
FINISHED |
| Object | A Star Is Born (1954 film) |
E21243
|
NE 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: A Star Is Born (1954 film) | Statement: [Born in a Trunk, featuredInTitleCharacter, A Star Is Born (1954 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInTitleCharacter Context triple: [Born in a Trunk, featuredInTitleCharacter, A Star Is Born (1954 film)]
-
A.
portrayedTitleCharacter
Indicates that one entity played the main or title role character associated with another entity (such as a work or production).
-
B.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
C.
featuredInPlotline
Indicates that an entity plays a notable or central role within a particular narrative plotline.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
representedInTitle
chosen
Indicates that an entity is mentioned or reflected in the title of another resource.
- F. None of above.
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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4104070a248190a2cf133105f95882 |
completed | June 28, 2026, 11:22 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.