Triple
T34185579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7314 |
E876948
|
entity |
| Predicate | hasMCGNumber |
P178497
|
FINISHED |
| Object | MCG −04-52-028 |
—
|
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: MCG −04-52-028 | Statement: [NGC 7314, hasMCGNumber, MCG −04-52-028]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMCGNumber Context triple: [NGC 7314, hasMCGNumber, MCG −04-52-028]
-
A.
hasMCR
Indicates a relationship where an entity is associated with, or possesses, a specific MCR (e.g., a defined minimum capital requirement or similarly named regulatory/technical measure).
-
B.
hasMC
Indicates that an entity has, features, or is associated with a main character (MC).
-
C.
hasMatrixNumber
Indicates that an entity is associated with a specific matrix identification number used to uniquely reference it.
-
D.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
-
E.
CMANumber
Indicates that there is an associated CMA (e.g., Case/Contract/Customer Management Agreement) identification number assigned to the entity or relationship.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.