Triple
T30388673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muon Package Manager |
E773013
|
entity |
| Predicate | supportsMultipleOrigins |
P207262
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Muon Package Manager, supportsMultipleOrigins, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleOrigins Context triple: [Muon Package Manager, supportsMultipleOrigins, yes]
-
A.
supportsCrossSiteRequests
Indicates that an entity allows or is compatible with making requests across different domains or origins.
-
B.
supportsMultipleWindows
Indicates that the subject can handle or display more than one window or view simultaneously.
-
C.
treatsAsCrossOrigin
Indicates that one entity is handled under the rules and restrictions applied to content from a different (cross) origin, rather than as same-origin.
-
D.
hasProposedOrigins
Indicates that there are suggested or hypothesized sources, beginnings, or origins for something, typically based on theory or evidence rather than certainty.
-
E.
supportsRedirects
Indicates that one entity enables or correctly handles redirect behavior for another entity or operation.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:01 p.m.