Triple
T33873737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M & M Productions |
E868294
|
entity |
| Predicate | handledTitle |
P178668
|
FINISHED |
| Object | The New Tenants |
—
|
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: The New Tenants | Statement: [M & M Productions, handledTitle, The New Tenants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledTitle Context triple: [M & M Productions, handledTitle, The New Tenants]
-
A.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
receivedTitle
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
D.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
E.
hadTitleSystem
Indicates that an entity possessed or was associated with a particular title within a specified system of titles.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:47 a.m.