Triple
T8022387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Policy |
E186767
|
entity |
| Predicate | supportsLinkingTo |
P33161
|
FINISHED |
| Object | site |
—
|
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: site | Statement: [Group Policy, supportsLinkingTo, site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLinkingTo Context triple: [Group Policy, supportsLinkingTo, site]
-
A.
supportsLinks
Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
-
B.
supportsRelation
Indicates that one entity provides assistance, endorsement, or structural backing to another entity or its activity.
-
C.
supportsLinkedData
chosen
Indicates that one entity provides or enables functionality for using, publishing, or interacting with Linked Data associated with another entity.
-
D.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
E.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.