Triple
T162833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Note |
E2946
|
entity |
| Predicate | canDocument |
P3129
|
FINISHED |
| Object | use cases |
—
|
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: use cases | Statement: [W3C Note, canDocument, use cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDocument Context triple: [W3C Note, canDocument, use cases]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
usedDocument
chosen
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
D.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
E.
canDeclare
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a2585a1a6481908899ad51211950e8 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2566392208190a538ea9aa1fac53e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.