Triple
T7933153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artifact Registry |
E184228
|
entity |
| Predicate | regionScoped |
P13939
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Artifact Registry, regionScoped, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionScoped Context triple: [Artifact Registry, regionScoped, true]
-
A.
regionContext
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
B.
locationScope
chosen
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
C.
regionReference
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
-
D.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
E.
regionImplied
Indicates that a broader or more general region is inferred or assumed from a given, more specific regional reference.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3acfd2a88190b1a13cd6fdedc272 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.