Triple
T7423188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TriG |
E171298
|
entity |
| Predicate | hasW3CStatus |
P74585
|
FINISHED |
| Object | Recommendation |
—
|
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: Recommendation | Statement: [TriG, hasW3CStatus, Recommendation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasW3CStatus Context triple: [TriG, hasW3CStatus, Recommendation]
-
A.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
B.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
-
C.
specificationStatus
chosen
Indicates the current approval or completion state of a specification within its lifecycle (e.g., draft, under review, finalized).
-
D.
hasOfficialWrittenStandard
Indicates that there exists an officially recognized and codified written standard governing how something (e.g., a language or system) should be represented in writing.
-
E.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2eece588190905774e7151edcb8 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.