Triple
T8286863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDGE |
E193805
|
entity |
| Predicate | supportsCodingSchemes |
P18653
|
FINISHED |
| Object | MCS-1 to MCS-9 |
—
|
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: MCS-1 to MCS-9 | Statement: [EDGE, supportsCodingSchemes, MCS-1 to MCS-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCodingSchemes Context triple: [EDGE, supportsCodingSchemes, MCS-1 to MCS-9]
-
A.
hasCodeScheme
chosen
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
B.
supportsRecordSchemas
Indicates that one entity is capable of handling, validating, or operating with specified record schemas defined by another entity.
-
C.
supportsCodeRates
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
D.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
E.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad3722481908076508908d18621 |
completed | March 31, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:52 p.m.