Triple
T14336191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MET |
E355472
|
entity |
| Predicate | issuerScope |
P113843
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [MET, issuerScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerScope Context triple: [MET, issuerScope, global]
-
A.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
-
B.
scopeClaim
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
C.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
D.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
E.
securityScope
Indicates the range or extent of protection, permissions, or access control that applies within a given security context.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.