Triple
T6443537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wasi-http |
E138282
|
entity |
| Predicate | hostLanguageAgnostic |
P33278
|
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: [wasi-http, hostLanguageAgnostic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostLanguageAgnostic Context triple: [wasi-http, hostLanguageAgnostic, true]
-
A.
languageIndependence
Indicates that a concept, method, or representation does not depend on any specific programming or natural language and can be applied uniformly across different languages.
-
B.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
C.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
D.
isLanguageIndependent
chosen
Indicates that the relationship, property, or behavior holds true regardless of the specific natural language used to express or encode it.
-
E.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.