Triple
T32344738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMK 3 |
E826424
|
entity |
| Predicate | networkMember |
P178359
|
FINISHED |
| Object | MMK 1 |
—
|
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: MMK 1 | Statement: [MMK 3, networkMember, MMK 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkMember Context triple: [MMK 3, networkMember, MMK 1]
-
A.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
B.
coMemberWith
Indicates that two or more entities share membership in the same group, organization, or collective.
-
C.
FCSMember
Indicates that an entity is a member of, or affiliated with, the FCS (e.g., a specific conference, system, or organizational group).
-
D.
killsMembersOf
Indicates that one entity causes the death of individuals who belong to a particular group or organization.
-
E.
duoMember
Indicates that an entity is one of the two participants forming a duo with another entity.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: May 1, 2026, 12:48 a.m.