Triple
T18942750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDA |
E463426
|
entity |
| Predicate | associatedWithFranchiseInception |
P27544
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [MDA, associatedWithFranchiseInception, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFranchiseInception Context triple: [MDA, associatedWithFranchiseInception, 1993]
-
A.
appliedToFranchiseFoundedIn
Indicates that something (such as a rule, policy, or action) is applied specifically to a franchise that was founded in a particular time or place.
-
B.
franchiseEra
Indicates the specific historical or operational period within which a franchise’s activities, rights, or identity are defined.
-
C.
franchiseDebut
Indicates the first appearance or introduction of an entity within a particular franchise or series.
-
D.
franchiseStart
chosen
Indicates the point in time or event at which a franchise or franchising relationship is initiated or begins.
-
E.
beganWithFranchise
Indicates that an entity originated or started as part of a particular franchise.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3ec857081908da0f974604f2c65 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.