Triple
T25248265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDDN |
E632660
|
entity |
| Predicate | hasNotableFounders |
P49137
|
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: [MDDN, hasNotableFounders, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFounders Context triple: [MDDN, hasNotableFounders, true]
-
A.
hasNotableFounder
Indicates that an entity was founded or established by a person or organization considered especially significant or noteworthy.
-
B.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
C.
hasFormerFounder
Indicates that an entity was previously a founder of another entity but no longer holds that founder role or status.
-
D.
notableFounderMembership
Indicates that an entity is notably recognized as a founding member of another entity, such as an organization, group, or initiative.
-
E.
notableFounderTeam
chosen
Indicates that the entity has a founding team whose members are particularly distinguished, prominent, or otherwise noteworthy.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 21, 2026, 1:10 p.m.