Triple
T1160481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | npm |
E24478
|
entity |
| Predicate | hasNamespace |
P25615
|
FINISHED |
| Object | @scope packages |
—
|
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: @scope packages | Statement: [npm, hasNamespace, @scope packages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamespace Context triple: [npm, hasNamespace, @scope packages]
-
A.
namedSpace
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
B.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
C.
hasSubspace
Indicates that one space is a subset or component of another, existing entirely within the larger space.
-
D.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
E.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.