Triple
T311126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTPS |
E7608
|
entity |
| Predicate | visibleIndicator |
P8487
|
FINISHED |
| Object | padlock icon in most browsers |
—
|
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: padlock icon in most browsers | Statement: [HTTPS, visibleIndicator, padlock icon in most browsers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleIndicator Context triple: [HTTPS, visibleIndicator, padlock icon in most browsers]
-
A.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
visibilityRequirement
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
C.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
D.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
-
E.
statusIndicates
chosen
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea49636c8190a69cbd951fc0a4db |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.