Triple
T38446750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XProtect |
E906659
|
entity |
| Predicate | visibilityToUser |
P74023
|
FINISHED |
| Object | mostly invisible during normal operation |
—
|
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: mostly invisible during normal operation | Statement: [XProtect, visibilityToUser, mostly invisible during normal operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityToUser Context triple: [XProtect, visibilityToUser, mostly invisible during normal operation]
-
A.
visibilityType
Indicates the kind or level of how visible something is, such as whether it is public, private, or restricted.
-
B.
visibilityControlledBy
Indicates that the visibility or hidden/shown state of one entity is determined or governed by another entity.
-
C.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
D.
visibilityStatus
chosen
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
E.
visibleBy
Indicates that one entity can be seen or perceived visually by another entity.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.