Triple
T29503778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic |
E748454
|
entity |
| Predicate | typicallyUsedOver |
P64034
|
FINISHED |
| Object | HTTPS |
—
|
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: HTTPS | Statement: [Basic, typicallyUsedOver, HTTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyUsedOver Context triple: [Basic, typicallyUsedOver, HTTPS]
-
A.
oftenUsedAfter
Indicates that one entity is frequently or typically used immediately following another entity in a sequence or workflow.
-
B.
frequentlyUsedBy
Indicates that something is regularly or commonly utilized by a particular entity.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
usedOver
chosen
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
E.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a01ccd995e48190b6675e463bd0a567 |
completed | May 11, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_6a01cc33177c8190bc0703276618b3ec |
completed | May 11, 2026, 12:31 p.m. |
Created at: April 28, 2026, 4:26 p.m.