Triple
T28328428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XSHG |
E717472
|
entity |
| Predicate | isPrimaryMICFor |
P180418
|
FINISHED |
| Object | Shanghai Stock Exchange |
—
|
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: Shanghai Stock Exchange | Statement: [XSHG, isPrimaryMICFor, Shanghai Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryMICFor Context triple: [XSHG, isPrimaryMICFor, Shanghai Stock Exchange]
-
A.
isMICFor
Indicates that one entity represents the minimum inhibitory concentration (MIC) value determined for another entity, typically a microorganism or drug.
-
B.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
C.
isPrimarySetFor
Indicates that one entity is designated as the main or default set associated with another entity.
-
D.
hasMICType
Indicates that an entity is associated with a specific Market Identifier Code (MIC) classification type.
-
E.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 28, 2026, 12:30 a.m.